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

Activate Subscription Bot Access Tokens

Activate a saved batch for your Telegram subscription bot or Discord subscription bot. Codes become usable only after this step succeeds.

POST/v2/projects/{project_id}/access-tokens/activate

Authorization

Bearer TokenRequired

Requires memberships:add for a human admin. Restricted project API keys need access-tokens:create. Use the same user or API key that prepared the batch.

Path Parameters

project_idstringrequired

The UUID of the project.

Request Body

activation_tokenstringrequired

The complete, unexpired activation ticket returned when preparing this batch.

Behavior and recovery

Use the same authenticated user or API key that prepared the batch:

Activation rechecks permissions, plan availability, and generation quota, then activates the entire batch. The response contains token-free metadata; it does not return the plaintext codes again.

Retry a lost activation response with the same ticket before it expires. This does not create another batch or reactivate revoked or redeemed codes. After expiry, list tokens and match the saved IDs to determine whether activation committed. Discard an unactivated draft to cancel it; its IDs cannot be revoked before activation.

The data array contains one metadata object per token. An initial activation returns 201; a completed activation retry returns 200.

Start with Prepare Tokens and use List Tokens to inspect activated IDs after an uncertain result.

Last updated: