Skip to main content
GET
Usage by token

Use Case:

If you resell Generect inside your own product, you probably issue one token per customer. This endpoint tells you what each of those tokens actually did, so you can bill the right customer, see who is close to their limit, and catch a broken integration before it shows up on your invoice. Ask for a single client with client_id, or leave it off to get every token at once. Tokens with no traffic in the period are still listed, at zero — useful for spotting a customer who has stopped using you.

Authorizations

Authorization
string
header
required

Use the required Token prefix. Example: Authorization: Token xxxxxxxxx

Query Parameters

client_id
string

Restrict the report to the token carrying this client identifier — the value set when the token was created.

token
string

Restrict the report to one exact token value.

start_date
string

Start of the reporting window. Accepts YYYY-MM-DD or a full ISO timestamp. Defaults to 30 days ago.

end_date
string

End of the reporting window, inclusive. Defaults to now. A date with no time means midnight, so end_date=2026-05-31 stops at the very start of the 31st and that day's traffic is not counted — pass 2026-05-31T23:59:59 (or the 1st of the next month) to include it.

timezone
string
default:UTC

IANA timezone used to render the period bounds in the response. It does not change which requests are counted: the default window is anchored to the same instant whichever zone you name. An unrecognised name is rejected with 400.

Response

Per-token usage analytics

data
object