Skip to main content
A key is created in the seller dashboard under Seller → API keys. It is shown once, and it acts on behalf of the account until it is revoked.

Sending the key

The key goes on every request. There are no intermediate tokens to exchange it for.
HTTPS only. A key that has travelled over plain HTTP should be treated as leaked and rotated.

What a key reaches

The seller’s own offers: list them (GET /v1/offers/my), create, edit, manage units, pause and archive. Anything the dashboard guards with a second factor — changing the account email, 2FA settings, withdrawals — is out of reach for a key.

Address allowlist

Optional. If your integration runs from fixed addresses, list them when you create the key (an address or a subnet, up to 16 entries) and the key is refused from anywhere else. An empty list means any address.

Rate limits

Going over returns 429. It is a temporary refusal: wait and retry, the key stays valid.

Rotating a key

An account holds up to 5 keys. Create the replacement before you need it: point your integration at the new key, confirm it works, then revoke the old one. Nothing has to go down in between.

Errors