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.
Examples
curl --request GET \
  --url https://api.botsubscription.com/v1/endpoint \
  --header 'Authorization: Bearer sk_live_•••'

Activate Subscription Bot Access Tokens

Activate every access code in a prepared batch for your Telegram subscription bot or Discord subscription bot. One request activates the entire batch, whether it contains 1 code or 100.

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

Authorization

Bearer API KeyRequired

API key scope: access-tokens:create (required for restricted keys).

Path Parameters

project_idstringrequired

The UUID of the project.

Request Body

activation_tokenstringrequired

The batch activation ticket from data.activation_token in the preparation response. This one string activates all codes in that batch; it is not an individual access code.

How batch activation works

The activation_token is one ticket for the whole batch. For example, preparing with count: 100 returns 100 access codes and one activation_token. Submit that ticket once to activate all 100 codes together.

  1. Prepare the codes and save each code and access_token_id, plus the batch's activation_token.
  2. Send the saved activation_token to this endpoint using the same project and API key, within 30 minutes of preparation.
  3. Redeem each activated code separately for its intended member, or distribute the codes privately.

Activation makes the codes redeemable. It does not grant membership or start the membership duration; that happens when a code is redeemed.

Preparation and activation are separate REST requests so you can save the secret codes before making them usable. Preparation has no immediate-activation option.

Retries and recovery

Activation rechecks the key's access, plan availability, and issuance policy. It returns metadata only, so keep the codes saved from preparation.

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.

Use List Tokens to inspect activated IDs after an uncertain result.

Note

Response examples use the UTC ISO date format.

Last updated: