Dashboard
APIMonthly Recurring Revenue | 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_•••'

Monthly Recurring Revenue

Read monthly recurring revenue snapshots based on proven paid membership coverage. Use this report for your Telegram subscription bot or Discord subscription bot project.

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

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 bucket is a snapshot at its end or the computation time, whichever is earlier. Totals repeat the final snapshot rather than adding buckets. Trials and payments without evidence of paid coverage are excluded and counted in disclosures. MRR normalizes paid value to 30.4375 days, sums exactly by currency, then rounds once to that currency's precision. More than 100,000 source payments returns 413; narrowing the window may not help because earlier paid coverage is still needed.

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

Last updated: