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.
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.
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.
Prepare the codes and save each code and access_token_id, plus the batch's activation_token.
Send the saved activation_token to this endpoint using the same project and API key, within 30 minutes of preparation.
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.
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.