Read this period's usage per channel
Try it — GET /account/usage
Kept for this tab only — it disappears when you close it, and it is never sent anywhere except as the Authorization header on the call below.
Authorization
bearerAuth account:readAuthorization: Bearer sk_live_.... Keys in the query string or the
request body are refused — a URL is logged by every proxy it passes,
and that is how customer keys leak.
A key carries scopes. A call outside them answers 403 with
insufficient_scope and names the scope it wanted.
In: header
Scope: account:read
Response Body
application/json
application/json
curl -X GET https://app.sendkuy.com/api/v1/account/usage \ -H "Authorization: Bearer sk_live_YOUR_API_KEY"{ "data": { "object": "account_usage", "id": "string", "type": "user", "period": {}, "usage": {} }}Read the account behind this key GET
Previous Page
Read the status of background work GET
Guarded by a key, but by **no scope at all** — the only route in v1 that is. A job is born from a call whose scope was already checked, so asking for its progress needs nothing further. Do not infer scopes from the pattern of other routes here.