Get a UCP merchant by domain or merchant id
Fetch a single UCP merchant by either its domain (e.g. shop.example.com) or
its merchant_id. The merchant_id is the short identifier returned on every
merchant resource; passing it resolves the merchant directly, so a caller that
already holds a record can look it up without knowing the domain.
A merchant_id is derived from the merchant’s domain, so a merchant that moves
to a new domain is issued a new one. Two domains could in principle derive the
same id, though it is vanishingly unlikely; were that to happen, the id would
resolve to one of them. Look up by domain when an exact match is required.
The two forms have different freshness guarantees. A merchant_id reads the
record directly and always sees the latest write. A domain is resolved through
the search index, which updates a moment later, so a newly indexed merchant may
briefly be retrievable by id before it is retrievable by domain.
ucp.services gives the endpoints the merchant’s UCP servers are reachable at, one
per service and transport. Those endpoints frequently sit on a different host from
the merchant’s domain.
Authorizations
Org-scoped key for the UCP Merchant Search endpoints. Sent in the x-sumvin-ucp-token header.
Headers
Controls how timestamp fields are serialized in JSON response bodies.
Default (header omitted or any other value): epoch milliseconds as integers.
iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.
Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".
Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.
Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.
"iso8601"