Games and social media have separate endpoints: games use /api/games and social media use /api/v1. Both use your existing SaltiBoost API key and wallet. Send form-encoded POST requests to https://saltiboost.com/api/games. Responses are JSON. Keep your API key on your server; never put it in a public website or URL.

Pricing: rate is per unit, not per 1,000. Charge = rate × quantity, rounded to four decimal places. Package quantity must be 1. For amount products use the returned min and max (null means no catalog maximum). max_charge optionally limits the total you agree to pay.

Player details: use the service and category IDs returned by services. The first required field is player_id. Supply additional fields by their returned key, for example extra_params[server_id]. Requirements differ by game.

Safe retries: client_reference is required, up to 64 letters, numbers, dots, underscores, colons or hyphens. Use a unique reference for each purchase. Retrying identical parameters with the same reference returns the existing order without charging again. Changing the parameters with the same reference returns an error.

Order flow: SaltiBoost reserves the wallet charge and returns an order ID. The scheduled worker submits automatic orders to the provider. Manual products are fulfilled by staff. Explicit provider rejection cancels the order, returns the charge to the wallet, and sends a cancellation email. Failed input validation or insufficient customer balance returns an error without creating an order.

Status: pending means queued; processing means fulfillment is in progress; completed means delivered; canceled means canceled. A pending_review response means the provider result is uncertain. Keep the same reference and contact support with the order ID; creating a new reference may duplicate a purchase. Email delivery depends on your mailbox and the site's email service.

List products

curl -X POST 'https://saltiboost.com/api/games' \
  --data-urlencode 'key=YOUR_API_KEY' \
  --data-urlencode 'action=services'

Create an order

Replace example IDs and quantities with values from services.

curl -X POST 'https://saltiboost.com/api/games' \
  --data-urlencode 'key=YOUR_API_KEY' \
  --data-urlencode 'action=add' \
  --data-urlencode 'service=SERVICE_ID' \
  --data-urlencode 'category=CATEGORY_ID' \
  --data-urlencode 'player_id=PLAYER_ID' \
  --data-urlencode 'quantity=1' \
  --data-urlencode 'client_reference=my-shop-order-123'

{"order":123,"client_reference":"my-shop-order-123","status":"pending","charge":"2.0000","currency":"USD","requires_review":false}

Check status

curl -X POST 'https://saltiboost.com/api/games' \
  --data-urlencode 'key=YOUR_API_KEY' \
  --data-urlencode 'action=status' \
  --data-urlencode 'client_reference=my-shop-order-123'

Errors return {"error":"Explanation"}. Provider rejection is reported through the order status after the cron processes it. Existing social-media API actions continue to work as before.