Skip to main content
The Seller API lets your backend read and manage one store: its orders, the delivery command queue, game servers, and webhook endpoints. Every request is authenticated with an API token that belongs to that store. The endpoint pages in this section are generated from the same contract the backend enforces. If a page and a response ever disagree, the response is right and the page is a bug.

​
Base URL

Send requests over HTTPS only. The API is available on the Enterprise plan.

​
Data format

Requests and responses use JSON with UTF-8 encoding. Send Content-Type: application/json on requests that have a body.

​
Omitted fields

A field that does not apply, or that your token has no scope to read, is left out of the response instead of being sent as null. For example, an order read without orders:buyer:read has no buyer field, and an order that never used a custom gateway has no customGateway field. Write your client so a missing field and a null field mean the same thing.

​
Resources

Authentication

Send the token and pick the scopes each integration needs.

Rate limits

Per-token limits, rate headers, and the executor cadence.

Errors

Problem details and every error code the API can return.

Pagination

Page through orders, commands, endpoints, and deliveries.

Webhooks

Receive signed order events instead of polling.

Changelog

What changed in the API and when.