This walks you from no key to a successful call and a successful write. It takes about five minutes.
1

Create a secret key

In your dashboard, open Settings, API keys and create a key. Grant it only what your integration needs. For this walkthrough tick Read on Products.Your key is shown once, at creation. Copy it then. Mercemur stores only a hash, so nobody can recover the value for you later, including support.
A secret key can read and change your store. Keep it server side. Never put it in a browser bundle, a mobile app, or a public repository.
2

Make your first read

Every request goes to https://api.mercemur.com/api/v1 and carries the key as a bearer token.
A successful list response has your records in data and paging state in page:
3

Handle the refusal you are most likely to hit first

If the key lacks the scope for the route, you get 403 and the message names the exact scope to tick:
Add the scope in the dashboard and retry. Scope changes apply to the existing key, so you do not need to issue a new one. See Scopes.
4

Make your first write

Writes need one extra header: a unique Idempotency-Key. It is required, not optional, and it is what makes a retry safe after a timeout.
Generate a fresh key per logical operation, and reuse that same key when you retry that operation. Replaying it returns the original response instead of creating a second product. See Idempotency.
This write needs write_products. Read and write are separate grants, so a key with only Read will be refused here.
5

Page through a full collection

There is no page or offset. You pass the previous response’s page.next_cursor back as after, and stop when has_more is false.
See Pagination.

Next

API reference

Every endpoint, with a playground bound to your own store.

Money

Read this before you send an amount. Every value is an integer in minor units.