Credit balance
The balance, where it is going, and when it runs out.
gethttps://api.integrable.cloud/api/credits
- Authentication
- Bearer token
- Retries
- Safe to repeat
- Body
- None
- Version
- 2026-09-03
Read together because they are shown together, with one balance read shared between the header and the forecast. The forecast is the part that changes behaviour: "1,240 credits left" invites no action, and "at this rate you run out on the 19th" does.
Values are in credits; totals also carry value_usd, the credits at the rate the customer buys them. No single action carries a dollar figure, and what an action cost us is never in this response.
Query parameters#
Responses#
Errors#
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.
More Insights endpoints#
Something unclear or missing? Tell us and we’ll fix it.