The Base Product Object
The Base Variant Object
A Base Variant represents a specific, orderable version of a Base Product. When placing a swag order you must always specify the variant ID - the Base Product id alone is not sufficient.Key Concepts & Business Rules
Swag Base Products vs standard Products
V3 exposes two related endpoint families:
The endpoint families use different response schemas and are not interchangeable.
Base Product → Base Variant → Order
The flow mirrors the marketplace flow: browse Base Products, drill into the Base Variants for the one you want, and place an order specifying the variant.Pagination
Base Product and Base Variant list endpoints use page-number pagination (page[number], page[size]):
See Request & Response Standards for the full V3 pagination contract.
Filtering
The Base Product list endpoint supports these JSON:API-style filters:filter[brandId]- comma-separated brand IDsfilter[brandName]- case-insensitive brand name searchfilter[tagId]- comma-separated tag UUIDsfilter[title]- case-insensitive title searchfilter[id]- comma-separated Base Product UUIDsfilter[color]- comma-separated color titlesfilter[size]- comma-separated size titlesfilter[printingTechnique]- comma-separated printing-technique names
400.
Location
All Base Product and Base Variant requests require a supported ISO 3166-1 alpha-2location query parameter.
Account scoping
All Base Product and Base Variant requests require theSnappy-Account-Id header.
Permissions
All Base Product and Base Variant endpoints require theproducts:read scope on your API key.
How to Work with Swag
List base productsinclude=brand,tags for related entities and fields=options for aggregated variant options.
Get a single base product
include and fields expansions as the list endpoint.
List base variants for a base product
include or fields.
Get a single base variant
include or fields.