Skip to main content
1

Get your client

A seller running their own script creates one themselves: Trader → Settings → Integrations. They get a client id and a secret, and the secret is shown once — we store only a hash of it.A product used by several sellers is registered by us instead. Mail support@wristler.eu with the name sellers will see on the consent screen and your redirect URI.
2

Ask for a token

A seller’s own script uses client credentials — no browser, no redirect:
A product several sellers connect to uses the authorization code flow with PKCE instead, so each seller approves you themselves. Both flows, in full →
3

Paste it into the playground

Every page in the API reference has a Bearer token field. Paste the access_token from the previous step into it and the console calls the API as you — it does not run the OAuth flow itself, which is why that step is a call of its own.Pick the environment from the server dropdown at the top of the page. A token is good for one environment: a production client id does not work on staging.
4

Check it works

This needs no scope. If it answers, your token is good.
5

Find the business you act for

Exactly the businesses that granted you access, and nothing else — so you never have to be told an id out of band. Every address below takes one of these ids.
6

Read their stock

Everything they have: drafts and sold listings included, which the public catalogue deliberately does not give you.

What to build next

Sync an inventory

Creating and updating listings, and the one field that makes the rest easy.

Pull orders

Incremental pulls, and recording a shipment.
Send an Idempotency-Key on every write you might retry. A network error tells you nothing about whether the write landed; that header does. How it works →