Skip to main content
GET /v1/usage returns everything your account is entitled to and how much of it you have consumed in the current billing cycle — plan, cycle dates, and a meter per resource. Use it to show a usage widget, to decide whether to submit an FFmpeg job, or to check how many profile slots are left before you mint a connect link.
Publishing is unlimited on every paid plan (see Posts), so uploads.limit is null — the used counter still runs as a meter, not a cap.

Request

The endpoint is scoped entirely to the key’s own account — it takes no parameters and can never return another account’s figures. It is a GET: it consumes no FFmpeg minutes and no uploads, only the per-minute rate limit.

Response

Meters

Every metered resource uses the same three fields:
Treat limit: null as unlimited, not zero — a remaining ?? 0 fallback will wrongly show your users as out of allowance.

Fields

Cycle dates

Your cycle is anchored to the day your plan was activated, evaluated in Vietnam time (UTC+7) — not the first of the calendar month. A plan activated on the 7th resets on the 7th. An anchor day that does not exist in a shorter month is clamped to that month’s last day. period.start and period.renews_on always report the real dates, so read them rather than computing month boundaries yourself.

Checking before you act

Errors

See Errors for the full reference.