Dashboard
APIAccess Code Activity | Subscription Bot API
api.botsubscription.com
GET/v1/endpoint
AuthenticationBearer
Token
Stays in this tab. Required for this endpoint — the value below is what gets sent.
Examples
curl --request GET \
  --url https://api.botsubscription.com/v1/endpoint \
  --header 'Authorization: Bearer sk_live_•••'

Access Code Activity

Read issued, claimed, and revoked access-code activity alongside current status counts. Use this report for your Telegram subscription bot or Discord subscription bot project.

GET/v2/projects/{project_id}/analytics/access-codes

Authorization

Bearer API KeyRequired

API key scope: analytics:charts:read for restricted keys. Unrestricted project keys also support this endpoint.

Path Parameters

project_idstringrequired

Project UUID.

Query Parameters

fromstring

First UTC calendar day, YYYY-MM-DD; default to minus 29 days.

tostring

Last UTC calendar day inclusive, YYYY-MM-DD; default today.

intervalstring

day (default), week (ISO Monday start), or month (calendar).

Dates must be real calendar days between 2000-01-01 and 2099-12-31, with from no later than to and at most 366 days inclusive. Unknown query parameters are rejected. There is no request body. See the shared analytics date, money, and cache rules.

Interpreting this report

Each activity uses its own timestamp. One code issued, claimed, and revoked in the window counts once in every corresponding series. Gauges ignore the window and classify each code once: billing pending, revoked, claimed, then unused. Revocation and gauge queries scan the project's codes, so their cost does not depend only on the window.

Use the project API authentication reference for API-key setup.

Last updated: