Skip to main content
General product catalog: licence keys, gift cards, subscriptions and more.
For a full mirror of the catalog (with delivery mode and stock) use GET /api/catalog. The endpoints below are the lighter, per-product calls.

1. Get all products

Get all available products with their variants. Endpoint: GET /api/products
Response

2. Get product variants

Endpoint: GET /api/products/{productId}/variants
Response
Variants where you hold a stock allocation also contain a client_stock object (details).

3. Purchase a product

Endpoint: POST /api/products/purchase/{variantId} Basic request (no inputs required):
With product inputs (when requires_input is true):
Response
Save order_ids before doing anything else. They are the only way to retrieve the code later.
Your wallet is debited and, for allocated variants, your stock is consumed in the same transaction. If anything fails, nothing is charged.

4. Retrieve order keys

Single order

Endpoint: GET /api/products/order/{orderId}
Response

Multiple orders

Endpoint: POST /api/products/orders/retrieve
Request
The response is an array of order objects in the same format as a single order.

Status values

If has_key is false, poll the endpoint until the key becomes available.

Example workflow

Input fields

Some products need extra data, for example game account details. Read the input_fields of the variant (or product in the catalog) and send those fields in the purchase body. Missing or invalid fields return a validation error.

Best practices

  • Read delivery and available first (delivery modes).
  • Check available_balance before large batches.
  • Poll orders/retrieve for processing orders and stop when the status is final.