Reseller API

Getting started

1. Verify your phone number. Your account must be at least 14 days old.
2. In Account → API press "Create my key" and enter the code sent to your phone. The key is shown only once — store it safely. You get an e-mail whenever a key is created.
3. Add balance. The API buys only with balance; if your balance is not enough, no order is created.

Tiers and limits

Limits rise automatically with your account's total purchases. See your current tier in GET /account and on Account → API.

The daily limit and spent_today count the full amount of every API order placed today: a refunded order still counts and a refund does not reopen the limit. On a product priced below a cent this amount can differ from total by up to half a cent per order.

If you need higher limits, contact our support team. Accounts with a card dispute (chargeback) permanently lose API access.

Authentication

Send the key only in a request header:

curl -H "Authorization: Bearer ftk_YOUR_KEY" https://followturk.com/api/v1/account

curl -H "X-API-Key: ftk_YOUR_KEY" https://followturk.com/api/v1/account

Endpoints

/products and /orders accept the query parameters page and per_page (max 100; default 50 for /products, 20 for /orders). /products also accepts category_id and type (e.g. discord_boost). Each takes a single value; an array (e.g. page[]=1) is refused with 422 invalid_query.

Account

Your balance, tier and limits. tier is 1, 2 or 3; it is "custom" when your limits were set for you separately. Amounts are in USD.

{ "success": true, "data": { "username": "...", "balance": 42.5, "currency": "USD", "tier": 1,
  "daily_limit": 25.0, "spent_today": 4.5, "remaining_today": 20.5, "requests_per_minute": 30 } }

Categories

Only categories that have API products are listed. Use id as category_id on /products. This endpoint is not paged.

{ "success": true, "data": [{ "id": 5, "name": "...", "product_count": 12 }] }

Products

{ "id": 26, "name": "...", "type": "discord_boost", "category": { "id": 5, "name": "..." }, "currency": "USD",
  "unit_price": 0.282, "min_quantity": 2, "max_quantity": 14, "in_stock": true,
  "delivery_mode": "async", "quantity_step": 2, "order_minimum": 0.5,
  "required_fields": [{ "name": "invite_link", "type": "string", "required": true, "max_length": 512, "rule": "...", "example": "https://discord.gg/abcd1234" }],
  "options": [] }

{ "id": 123, "name": "...", "type": "code", "category": { "id": 7, "name": "..." }, "currency": "USD",
  "price": null, "variants": [{ "id": 789, "name": "...", "unit_price": 4.5, "min_quantity": 1, "max_quantity": 50, "in_stock": true }], "in_stock": true,
  "delivery_mode": "instant", "quantity_step": 1, "order_minimum": 1, "required_fields": [], "options": [] }

Product types and buyer input

Every product carries type, delivery_mode, required_fields and options. The price is the same as on the website. Buyer input, delivery and refunds are too, with three differences: on Steam you send your end customer's customer_ref; an MM2 item is delivered directly as a code; and when a code cannot be handed over, the website keeps the amount and the team delivers the code later, while the API returns the amount to your balance at once. For quantity limits and available options, min_quantity, max_quantity and options in the product reply apply.

• invite_link: Discord server invite (discord.gg/<code>, discord.com/invite/<code> or the bare code). It must never expire and have no use limit. An invalid or expired invite is refused with 422 field_invalid.
• gamepass_link: An RBL gamepass link priced at EXACTLY the ordered quantity, on sale, regional pricing off (or the link of a public game that has such a gamepass). A bare username is not accepted. A link that does not fit is refused with 422 field_invalid before any money moves.
• options.delivery: Only when the product lists it in options: boost (default, needs invite_link) or code (a boost code is delivered; do not send invite_link). An option that is not listed is refused with 422 unknown_option.
• customer_ref: Steam: your own id for the end customer (1-64 letters, digits, "_" or "-"). Always send the same value for the same person: that person gets one account per game and cannot buy the same game twice (409 already_owned). Upper and lower case differ: Ali and ali are two people.
• options.selection + options.amount: Account products priced by a choice: selection = skins, be or level (those listed in the product's options), amount = a whole number inside that selection's range (sent as a string). The price table is in the product's pricing field; the exact amount is computed on the order.
• in_stock: Whether the product can be bought right now (yes/no). No quantity is given.

order_minimum is the smallest order amount when the product is bought alone (0.50 USD for Discord products). Rbx quantity goes up to the product's max_quantity; at most 5 Rbx lines per order.

Place an order

Send a unique Idempotency-Key header with every order (8-64 chars: letters, digits, "-" or "_"). Resending with the same key never creates a second order; it returns the first one, so retrying after a network error is safe.

curl -X POST https://followturk.com/api/v1/orders \
  -H "Authorization: Bearer ftk_YOUR_KEY" \
  -H "Idempotency-Key: order-20261012-0001" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"product_id":123,"quantity":2},{"product_id":456,"variant_id":789,"quantity":1}]}'

curl -X POST https://followturk.com/api/v1/orders \
  -H "Authorization: Bearer ftk_YOUR_KEY" \
  -H "Idempotency-Key: boost-20261103-0001" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"product_id":26,"quantity":4,"fields":{"invite_link":"https://discord.gg/abcd1234"}}]}'

Reply

A new order answers 201. Resent with the same Idempotency-Key the answer is 200 with meta.replayed = true. The fields are explained under Read an order.

HTTP 201
{ "success": true, "data": { "order_number": "FT1A2B3C4D", "status": "completed", "total": 9.5, "currency": "USD", "created_at": "2026-11-05T12:00:00+03:00",
  "items": [{ "line": 1, "product_id": 123, "name": "...", "type": "code", "quantity": 2, "unit_price": 4.75, "total": 9.5, "status": "delivered" }] } }

HTTP 200
{ "success": true, "data": { ... }, "meta": { "replayed": true } }

Delivered accounts and codes are not in the create response; fetch them with GET /orders/{order_number}.

Read an order

Delivery details come only in GET /orders/{order_number}. Reading accounts and codes this way counts as taking delivery, just like on the website.

{ "success": true, "data": { "order_number": "FT1A2B3C4D", "status": "completed", "total": 9.5, "currency": "USD", "created_at": "2026-11-05T12:00:00+03:00",
  "items": [{ "line": 1, "product_id": 123, "name": "...", "type": "code", "quantity": 2, "unit_price": 4.75, "total": 9.5, "status": "delivered", "delivery": ["AAAA-BBBB", "CCCC-DDDD"] }] } }

total is what really left your balance, the same amount as your transaction record. On a product priced below a cent this amount can change by 1 cent with your balance, so always keep your accounts with the total in the reply. On an order with several lines each line total is rounded on its own and they can add up to a different amount; the order's total is the amount that counts.

Line fields

Line status

async lines move on within minutes; poll the order at a sensible interval (e.g. once a minute).

{ "line": 1, "type": "discord_boost", "quantity": 4, "status": "needs_input",
  "input_required": { "fields": ["invite_link"], "actions": [], "reason": "invite_invalid", "screening_ack_required": false } }

{ "line": 1, "type": "account", "quantity": 2, "status": "delivered", "delivery": ["login:password", "login:password"] }
{ "line": 1, "type": "account", "quantity": 5, "status": "partial", "delivery": ["login:password", "login:password"] }
{ "line": 1, "type": "code", "quantity": 3, "status": "partial", "refund": { "amount": 2.5 }, "delivery": ["AAAA-BBBB", "CCCC-DDDD"] }
{ "line": 1, "type": "discord_members", "status": "delivered", "delivery": { "link": "https://…" } }
{ "line": 1, "type": "discord_boost", "status": "delivered", "progress": { "delivered": 4, "target": 4 } }
{ "line": 1, "type": "discord_boost", "status": "delivered", "delivery": { "code": "...", "boosts": 4, "period": "1m", "expires_at": "..." } }
{ "line": 1, "type": "robux", "status": "delivered", "delivery": { "robux": 1000 } }
{ "line": 1, "type": "steam_shared_account", "status": "delivered", "customer_ref": "shop-9921", "delivery": { "login": "...", "password": "...", "guard": { "available": true, "method": "mafile" } } }
{ "line": 1, "type": "mm2_item", "status": "delivered", "delivery": { "quantity": 2, "codes": [{ "code": "...", "quantity": 2, "name": "..." }] } }

The shape of delivery follows the line's type: accounts and codes = a list of texts; Discord members = link; Discord boost = code (or only progress); Rbx = robux; Steam = login, password, guard; MM2 = codes. When a delivery was handed over as plain text, delivery is a list of texts on any type (Steam, Discord members and MM2 too); on Rbx and MM2 such texts can also come in a details field. progress appears only once sending has started.

A partial refund (refund.amount) does not hide delivered accounts, codes or links, and the line keeps its delivery status. Delivery details are hidden only when the whole line or the whole order is refunded.

Order status

Order status: processing (work is going on for at least one line), needs_input (at least one line waits for input), completed (nothing more will happen; read the lines, some may be refunded), refunded (the whole amount went back to your balance), cancelled (if the amount did not come back, contact support), failed (no line could be delivered; contact support) or on_hold. You can stop polling on completed, refunded, cancelled and failed. on_hold is temporary: the order can go on after the review, so keep polling.

If the key that placed the order was rotated or deleted: for orders under 7 days old the new key receives the delivery details. For older orders the line status is shown but delivery is not, an MM2 item is not turned into a code, and Steam Guard answers 409 not_available_for_this_key. You reach those deliveries from your account on the website.

Send input

Works only on a line with status = needs_input and takes no money. It is the same action as "fix the link / try again" on the website's order page, with the same limits.

curl -X POST https://followturk.com/api/v1/orders/FT1A2B3C4D/lines/1/input \
  -H "Authorization: Bearer ftk_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"fields":{"invite_link":"https://discord.gg/newcode"}}'

-d '{"action":"retry","screening_ack":true}'
-d '{"fields":{"gamepass_link":"https://…/game-pass/123456789/My-Pass"}}'

The reply returns the updated order without delivery details; meta.line is the line that was handled. DC Boost: 5 attempts per line and 20 per account per hour; Rbx: 15 checks and 3 sends per 10 minutes.

While ordering through the API is closed, this endpoint is closed too (503 orders_disabled or orders_paused).

MM2 items

An MM2 line is delivered directly as codes; no extra call is needed. After the order the line is processing; when the codes are ready it becomes delivered and the codes are in delivery.codes of GET /orders/{order_number} (code, quantity, name). The codes are redeemed at followturk.delivery; hand the code to your end customer.

{ "line": 1, "type": "mm2_item", "quantity": 2, "status": "processing" }

{ "line": 1, "type": "mm2_item", "quantity": 2, "status": "delivered",
  "delivery": { "quantity": 2, "codes": [{ "code": "...", "quantity": 2, "name": "..." }] } }

• Reading the order again returns the same codes; it makes no new code and takes no money.
• The code is created the first time you read the order after the line is delivered (GET /orders or GET /orders/{order_number}). If you took the item into the game from your account on the website before that, there is no code for it: delivery.state = withdrawn_on_site.
• If the order cannot be placed in this quantity you get 409 out_of_stock; the reply does not say which line or how many. For a product that is on sale, these refusals for a quantity that does not fit are limited to 5 per hour per account: past that the same attempt gets 429 rate_limited, and the Retry-After header and details.retry_after say how many seconds to wait. An order in a quantity that can be bought is not affected by this limit. A refusal for a product the catalogue shows as in_stock: false is not counted.
• If an item cannot be prepared for a long time the line becomes in_review; our team looks at it and refunds it if needed (refunded). The codes are no longer shown on a refunded line.

Steam Guard

Gives a Steam Guard code for the account of a delivered Steam line; takes no money. The allowance is per line, as on the website: the first code opens a session in which a set number of codes can be taken, then the allowance locks (details.unlock_at). A failed request costs nothing. Your account also has a daily ceiling (delivered Steam lines × the per-line allowance); when it is reached you get 429 guard_daily_limit with details.unlock_at. The body must be empty, {} or []; anything else is refused with 422 invalid_body and costs nothing.

curl -X POST https://followturk.com/api/v1/orders/FT1A2B3C4D/lines/1/steam-guard \
  -H "Authorization: Bearer ftk_YOUR_KEY" -H "Content-Type: application/json" -d '{}'

{ "success": true, "data": { "line": 1, "code": "AB12C", "method": "mafile", "expires_in": 30,
  "quota": { "used": 1, "max": 7, "remaining": 6, "unlock_at": "..." } } }

The account (login, password and, when needed, ea) is read live on every GET /orders/{order_number}; a changed password shows the new one. If it cannot be read for a moment, delivery = {"state": "temporarily_unavailable"}.

Reply format and error codes

{ "success": true, "data": { ... }, "meta": { "page": 1, "per_page": 50, "total": 120, "total_pages": 3 } }

{ "success": false, "error": { "code": "insufficient_balance", "message": "Insufficient balance.", "details": { "required": 12.5, "balance": 4 } } }

API key

Applications and key management live in Account → API.