Skip to main content
The GET /v1/merchants/{id} endpoint returns the full profile for a single merchant. The {id} path parameter accepts several formats:

Endpoint

Parameters

string
required
Merchant identifier — accepts an integer ID, nmer_ ULID, mer_ canonical ULID, short slug, or a human-readable slug set in Merchant Manager.
integer
Set to 1 to return the extended merchant object — providers, canonical, categories, countries, currencies, supports, supports_deeplinking, cookie_duration, home_url, object_id, and slug. Use the integer 1, not true.
Pass extended=1 on every request. Whether the extended fields come back by default depends on your account, so don’t assume they will. It’s harmless if your account already returns them. If the response is missing providers or commissionable links, add the flag.

How to find a merchant’s ID

If you don’t already have a merchant’s ID, use the list or search endpoint first:
  1. Call GET /v1/merchants?search=merchant+name to find the merchant.
  2. Copy the id or object_id from the matching result.
  3. Use that value in GET /v1/merchants/{id} for direct lookups.
Store object_id (nmer_ format) rather than the integer id — it is stable across system migrations.

Example requests

Integer ID
nmer_ ULID
Canonical ID

Response

Response fields

See List Merchants — Response fields for the full field reference. The single-merchant response uses the same object shape.

Error responses