Per-subject usage for a period

Paginated per-subject feature-usage counts for one billing period.
PLATFORM-KEY ONLY — a subject token is rejected with 403, the same
as every other endpoint on this surface that isn't

GET
/subjects/{subject}/sites

or a sites operation: this is an
account-wide report across ALL of your end-users, not something one
end-user's own token may read.

REPORTING ONLY. upload.tf bills your platform ACCOUNT (one Polar
customer per account); it never bills, meters overage against, or
creates a Polar customer for an individual subject. This endpoint
exists solely so you can see which of your subjects drove usage, in
order to rebill them yourself. Only FLOW meters are ever reported per
subject — today, site_build. The stock hosted_site meter (live
hosted-site count) is a whole-ACCOUNT high-water-mark gauge with no
per-subject breakdown to report here; if you need one subject's
current site count, count the results of

GET
/subjects/{subject}/sites

instead.

Pagination is a KEYSET cursor (nextCursor), not offset-based —
opaque, pass it back as ?cursor= to fetch the next page. Absent
nextCursor (null) means you've reached the last page.

API Key

Add parameter in header

x-api-key

Example:

x-api-key: ********************

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

{ "success": true, "data": { "period": "string", "subjects": [ { "subjectId": "68460e63-0717-47f9-8fd8-d28f152cb30b", "externalId": "string", "features": { "site_build": 42 } } ], "limit": 0, "hasMore": true, "nextCursor": "string" } }

Request

Responses