This month's usage and what it would cost
Counted as it happens rather than derived at the end of the month, so this is the same number the invoice will use.
Over quota, opening is refused and closing is always allowed. A billing problem must never hold you in a position you cannot exit — an order to close comes back 201 however far over the plan you are, and only opening returns 402 QUOTA_EXCEEDED.
Authorization
apiKey Authorization: Bearer fx_live_<id>_<secret>.
A key is shown once, at creation. We cannot show it again or recover it for you.
Keys carry an environment (live or test) in the key itself, so a test key pasted into a
production config fails immediately instead of at the worst possible moment.
Scopes are per key. A key without accounts:write can read accounts and nothing else.
In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/billing/usage"{ "data": { "plan": "string", "planName": "string", "currency": "string", "subtotal": null, "overage": 0, "total": null, "entitlements": { "accounts": 0, "ordersPerMonth": 0, "wavesPerMonth": 0, "legsPerWave": 0, "apiCallsPerMonth": 0, "allowOverage": true }, "features": { "executionWaves": true, "pendingOrders": true, "alwaysOn": true, "webhooks": true }, "usage": { "orders": 0, "waves": 0, "api_calls": 0, "accounts": 0 } }}The available plans GET
The plans on offer now: what each includes and what it costs. Prices are in minor units — `9900` is $99.00, never a float. `accounts` is a capacity limit: you cannot exceed it and be billed for the excess. The monthly allowances can run over where the plan allows it, up to twice the allowance, after which orders are refused — a runaway strategy should not be able to generate an unbounded invoice.
Usage broken down by day GET
For a chart, or for checking an invoice line against the day it came from.