Reseller API - developer documentation

Last updated:

Reseller API - developer documentation
Connect your own shop, bot or panel directly to SuperCoinsy. Check live stock and prices, place and pay for orders, follow their status and message our team - all without opening the reseller panel. Below you will find everything your developer needs: how to get access, how to authorize requests and what every endpoint returns.
What you need before you start
An active reseller account
The API works on top of your reseller balance. Orders are paid from it, so top up before your first call.
API access enabled by our admin
This is a one-time switch on our side. Write to [email protected] or message us on Discord at supercoinsy and we will turn it on for your account.
A fixed IP address
Every API user is bound to the IP it may connect from. Have it ready before you create your first token.
How to get your access token
1
Ask us to activate API access on your reseller account - see the contacts above.
2
Once it is active, open supercoinsy.com/account/reseller/api-users - this is where you manage all your API users.
3
Click CREATE and enter the IP address you will connect from. Requests from any other address are rejected. You may enter * to skip IP verification, but you do so at your own risk. This works in API v1 only.
4
Copy the 60-character token and store it somewhere safe. It is shown once and cannot be displayed again. Next to it you will also see a 6-character identifier - it labels your API user in our operation logs.
5
Click Turn ON in the table to activate the API user. From now on the connection will work. You can switch it off temporarily or delete it permanently at any moment.
You can keep several API users side by side - for example one for your production shop and one for testing - each with its own IP and its own token.
Authorization
Authorization goes in the request headers. Every request must carry all three, and must come from the IP assigned to that API user.
Content-Type: application/json
X-Authorization: <your 60-character token>
X-UserID: <your 6-character identifier>
Base address
All endpoints live under https://supercoinsy.com/uk/api/ and every response is JSON.
Endpoints (click to expand)
GET - Available stock
Check what we can deliver right now, per platform. A good first call before you expose a buy button in your own shop.
GET https://supercoinsy.com/uk/api/reseller/available-stock
Response
{
  "status": 1,
  "data": [
    { "platform": "PC", "stock_available": 10 },
    { "platform": "PS5, PS4, XSX, XSS, XONE, Stadia", "stock_available": 10 }
  ]
}
GET - Current prices
Your current reseller price per platform. Pull it regularly rather than hard-coding values, so your margins stay where you want them.
GET https://supercoinsy.com/uk/api/reseller/prices
Response
{
  "status": 1,
  "data": [
    { "platform": "PC", "price": "1.00" },
    { "platform": "PS5, PS4, XSX, XSS, XONE, Stadia", "price": "2.00" }
  ]
}
POST - Place and pay for a new order
Creates the order and settles it against your reseller balance in one call. If the balance is too low, the order is not created.
POST https://supercoinsy.com/uk/api/reseller/new-transaction
Parameters
quantity (required) - amount in K, so 150 means 150 000 coins.
platform (required) - pc or ps. Note that ps covers every console: PlayStation, Xbox and Stadia alike.
emailapp (required) - the EA account e-mail used to log in to the Web App.
passapp (required) - the password to that EA account.
codesapp (required) - EA backup codes, comma separated. Send at least three fresh ones.
userorderid (optional) - your own order reference; it comes back as your_id.
usernotes (optional) - a note for our team.
Request body
{
  "quantity": 150,
  "platform": "pc",
  "emailapp": "[email protected]",
  "passapp": "pass-app-test1",
  "codesapp": "one, two, three",
  "userorderid": "MY-ID2586",
  "usernotes": "please process quickly"
}
Response
{
  "status": 1,
  "message": "Payment accepted",
  "number": "R_QWERTY"
}
Store the returned number
The value in number is the identifier for every later call - details, messages and cancellation all use it.
GET - List of transactions
Returns your orders page by page, newest first. Use it to keep your own database in sync.
GET https://supercoinsy.com/uk/api/reseller/list-transactions?page=1
page (optional, integer) - defaults to the first page. The response tells you how many pages there are in total.
Response
{
  "total": 10,
  "pages": 1,
  "orders": [
    {
      "number": "R_ABCDEF",
      "placed": "2021-08-17 16:11:57",
      "your_id": "",
      "platform": "PS5, PS4, XSX, XSS, XONe, Stadia",
      "quantity": 100,
      "status": "Paid, waiting for delivery",
      "max_delivery_time": "2021-08-17 18:11:57"
    }
  ]
}
GET - Transaction details
Everything we hold on a single order, including the data you sent us and the deadline we are working to.
GET https://supercoinsy.com/uk/api/reseller/get-transaction/{identifier}?currency=EUR
identifier (required) - the order number, for example R_ABCDEF.
currency (optional) - EUR or USD. Defaults to EUR.
Response
{
  "number": "R_ABCDEF",
  "your_id": "TEST123",
  "placed": "2021-08-17 16:11:57",
  "value": "6.40 EUR",
  "platform": "PS5, PS4, XSX, XSS, XONe, Stadia",
  "quantity": 100,
  "emailapp": "[email protected]",
  "passapp": "test_pass",
  "usernotes": "notes-example-text",
  "codesapp": "test_code",
  "status": "Paid, waiting for delivery",
  "max_delivery_time": "2021-08-17 16:11:57"
}
POST - Send a message to an order
Adds a message to the order thread, exactly as if you had written it in the reseller panel. Use it to send fresh backup codes or to flag anything our team should know.
POST https://supercoinsy.com/uk/api/reseller/transaction/{identifier}/message
Request body
{
  "message": "My new message to the order"
}
Response
{
  "status": 1,
  "message": "Message has been sent"
}
GET - Cancel an order
Sends a cancellation request. It is a request, not an instant cancellation - our admin approves it, and only then is the amount returned to your EUR balance.
GET https://supercoinsy.com/uk/api/reseller/cancel-transaction/{identifier}
Response
{
  "status": 1,
  "message": "A cancellation request has been sent. SC Points will be refund to your account after approval by the admin."
}
API v2 and webhooks
API v2 runs next to v1, and v1 does not change. v2 adds more products, balance and balance history, exports and webhooks. Which products you can order depends on your account: GET /products lists them.
Own token and base address
API v2 has its own API users. Create them in the reseller panel under API & webhooks (supercoinsy.com/account/reseller/api-v2). A v2 token starts with sc2_ and works only in v2; a v1 token does not work there. The headers are the same: X-UserID and X-Authorization. Every API user needs a list of allowed IPs: an empty list refuses every request. Limits: 120 requests per minute per API user and 300 per reseller account.
https://supercoinsy.com/uk/api/reseller/v2
Endpoints
GET   /stock
GET   /prices
GET   /products
GET   /orders
POST  /orders          (header Idempotency-Key, up to 20 items, all or nothing)
GET   /orders/{id}
PATCH /orders/{id}/account
POST  /orders/{id}/cancel
GET   /orders/{id}/proof
GET   /orders/{id}/messages
POST  /orders/{id}/messages
GET   /division-rivals/quote
GET   /balance
GET   /ledger
GET   /topups
POST  /exports
GET   /exports/{id}
GET   /webhooks
PUT   /webhooks
POST  /webhooks/rotate
POST  /webhooks/test
GET   /webhooks/deliveries
Errors come as JSON with error and message. The full list with examples is on the docs page in the panel: supercoinsy.com/account/reseller/api-v2/docs
Differences from v1
  • Quantity. Coins: quantity_k, in thousands (150 means 150 000 coins). Codes, accounts and other catalogue products: quantity, a whole number of items (150 means 150 items). GET /products shows the form fields of every product.
  • Platform. Coins: pc or ps. Boosting: pc, ps or xbox (xbox is for Xbox-only boosting). For products with one console price, ps covers PlayStation and Xbox.
  • Backup codes (coins). At least 2, we recommend 6.
  • Cancel. POST /orders/{id}/cancel refunds at once when nothing has started. Once delivery has started, it is a request that our team confirms.
  • IP list. Public addresses and ranges (IPv4 not wider than /16, up to 20 entries). The * wildcard works only in v1.
Webhooks
  • Set one https address in the panel (API & webhooks) or with PUT /webhooks. Port 443, a host name (not an IP address), no redirects.
  • Pick the events: order.created, order.status_changed, order.needs_action, order.delivered, order.cancelled, export.ready.
  • We send a POST with a JSON body: id (the event id), event, created_at and data. For order events data is the order, in the same format as the API. For export.ready it holds id (the export id), kind and ready_at. For webhook.test it holds test: true and sent_at.
  • Headers: X-SC-Event, X-SC-Delivery and X-SC-Signature.
  • Check the signature: X-SC-Signature is t=<unix time>,v1=<hex>, where v1 is the HMAC-SHA256 of "<t>.<body>" with your secret (whsec_...). The secret is shown once; POST /webhooks/rotate issues a new one.
  • Answer with any 2xx within 4 seconds. Otherwise we retry after 1, 5, 15, 60 and 240 minutes; after 6 attempts the delivery is marked failed.
  • If more than 1000 events wait for your address, we switch the webhook off and email you. Fix the address and switch it on again in the panel.
  • POST /webhooks/test sends a webhook.test event. GET /webhooks/deliveries shows the latest deliveries (up to 100; entries are kept 30 days).
  • Webhooks exist only in API v2. API v1 has no webhooks.
{
  "id": "<event id>",
  "event": "order.delivered",
  "created_at": "2026-11-05T10:15:00Z",
  "data": { "id": "R_A2B3C4", "type": "coins", ... }   (order event)
}
A few things worth knowing
API v1: quantity is always in K
Send 150 when you mean 150 000 coins. Sending the full number would create an order a thousand times larger than intended.
API v1: "ps" means every console
There are only two platform values. Xbox and Stadia orders go in as ps, together with PlayStation - they share one delivery pool.
Backup codes are single use
Send at least three fresh codes with every order in v1. Codes already used on an earlier order will not let us log in, and the order will wait until you send new ones.
Status changes: polling in v1, webhooks in v2
API v1 has no callback, so check the order list or the details endpoint on a sensible interval rather than in a tight loop. API v2 can call your server when a status changes: see the webhooks section above.
One token, one IP
If your server changes address, edit the API user first - otherwise every request will simply be refused. And if a token leaks, switch that user off and create a new one.
Stuck on something?
If a request behaves differently than described here, tell us what you sent and what came back - we will look at the logs on our side. Write to [email protected] or ping us on Discord at supercoinsy.
Not integrating yet?
Everything the API does can also be done by hand in the reseller panel - topping up the balance, placing orders, following their status.
Reseller panel guide →
Ready to connect? Create your API user at supercoinsy.com/account/reseller/api-users
deliver
Check

Order or selling order status