Skip to main content
Use these selectors on GET /api/public/v1/brands/{brand}/{collection}. If you already have an ID, use the detail endpoint shown in API Reference. For code, tracking, and invoice examples, start with Find records by business identifiers. All selectors below are optional and combine with AND. Matches are filtered before pagination, and totalItems counts the full matching set. Responses retain the standard { items, nextCursor, totalItems } shape, even for a unique match. Collections also accept limit and cursor; see pagination. Text lookups are exact and case-sensitive, with literal spaces and punctuation. Product q is a case-insensitive literal substring search. Document-type domain is case-insensitive. Boolean selectors use true or false; integer selectors use whole numbers from 0 to 2147483647 without leading zeros. IDs ending in Id use the identifier format in API Reference, usually UUIDs. Unknown selectors return 400.

Pick the right scope

  • A lookup only returns records visible to your key’s brand. A matching code does not override visibility or include deleted records.
  • Supplier status and Partner partnerStatus describe the partner’s status. Suppliers still require an active link to the brand.
  • containerNumber on shipments matches an element of containerNumbers. categoryId on packing templates matches an element of categoryIds.
  • Document metadata selectors apply to /documents lists. Keep subject subjectKind and subjectKey together when reading a particular attachment. dataValue and issuerName match populated native document metadata; legacy attachments without those values do not match. Images use filename, while documents use fileName, matching each resource’s response fields.
  • Child and join collections use parent IDs and related IDs when they have no independent code. See entity relationships for joins.

Catalog

Sourcing and samples

Orders and production

Logistics and receipts

Invoices and payments

Partners and locations

Files and notes

Reference data