Charge order
On this page
Which two credit pools can pay for an API call
A Manage Bet Codes API call can draw from API credits (monthly API plan credits plus purchased packs, never AI credits, paying only for API actions) or regular credits (5 lifetime API test credits on Free, or Starter, Pro, or Tipster daily action credits shared by web and Telegram). Inside API credits the API spends the monthly plan first then the packs, and GET /v1/usage shows the plan source, balances, and api_credits.plan as null without an API plan.
- API credits: the monthly API plan credits plus purchased API packs. They are not AI credits. They pay only for API actions.
- Regular credits: 5 lifetime API test credits on Free (separate from the daily web and Telegram pool), or Starter, Pro, or Tipster daily action credits shared by the web app and Telegram.
Which charge_order value should my key use
Set one charge_order per Manage Bet Codes API key: api_first (default) spends API credits then regular credits, plan_first spends regular credits then API credits and can drain web and Telegram credits, api_only spends API credits only and returns 429 api_quota_exhausted when empty, and plan_only spends regular credits only and returns 429 plan_quota_exhausted when empty.
| `charge_order` | Charge order | When the first pool is empty |
|---|---|---|
api_first (default) | API credits, then regular credits | Regular credits |
plan_first | Regular credits, then API credits | API credits |
api_only | API credits only | 429 api_quota_exhausted |
plan_only | Regular credits only | 429 plan_quota_exhausted |
How to change charge_order on the dashboard
Change charge_order for each Manage Bet Codes key on the dashboard, which shows both balances next to the setting. The API never spends AI credits, and plan_only keeps the regular API rate limit with no jobs while an API plan unlocks higher limits and jobs.
Which extra charge rules apply to batches, jobs, and refunds
A Manage Bet Codes user can hold a regular plan and an API plan at once, and any verified user can create a key that spends regular credits without an API plan. Failed calls refund credits to the source that paid, batches charge 2 credits per target in target order, and jobs charge each item at start with refunds for failed items.
- A user can hold a Pro plan and an API plan at the same time.
- Any verified user can create a key.
- A key without an API plan spends regular credits.
- A failed call refunds its credits to the source that paid.
- A batch charges 2 credits for each target, in target order.
- A job charges each item when the item starts. A failed item is refunded.