Skip to main content
GET
GET /v1/usage/breakdown Requests and credits of the calling key per endpoint over the last days days, heaviest first: which routes consume your budget. Streams appear alongside REST routes, as WS <channel> (one row per channel, WS trades, WS token-updates…) and WS /v1/stream (connection minutes, free: always 0 credits), and price webhooks as WEBHOOK price (1 credit per trigger sent to your URL, requests = triggers sent). Free: never billed, and still reachable when the monthly credit allowance is exhausted. A key only ever sees its own usage.
Up to 100 routes, sorted by credits, then requests. Each row is { route, requests, credits }; on WS /v1/stream, requests is connection minutes (0 credits); on WS <channel>, credits follows the Streams billing and requests is the number of billed messages, including those that came to 0 credits; messages that are free by nature (replays of messages you already had, the periodic and resync states) are not counted.

Authorizations

Authorization
string
header
required

Your raw API key (not needed on the demo server).

Query Parameters

days
integer
default:30

1 to 90. Default 30.

Required range: 1 <= x <= 90

Response

200

Standard { data, meta } envelope.