Dashboard
APIPlan Performance | 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_•••'

Plan Performance

Compare completed sales and revenue by plan alongside current active memberships. Use this report for your Telegram subscription bot or Discord subscription bot project.

GET/v2/projects/{project_id}/analytics/plans

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.

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

Plans appear when they have sales in the window or active memberships now. Rows sort by completed sales descending, then plan ID. Active counts ignore the requested window. A hidden plan name is null for restricted keys; unrestricted keys can read it. Missing catalog rows also have null names. More than 200 qualifying plans returns 413, even when a shorter window cannot reduce the active-plan count.

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

Last updated: