Interacting with our APIs

Every Takion endpoint speaks plain HTTPS and shares the same authentication, the same subdomain pattern, and the same error codes. Learn it once here, then each vendor page only covers what is uniqueL

API Key

You need an API key to call any endpoint. Request a trial key via Discord or purchase a plan.

A key looks like this:

TAKION_API_XXXXXXXX

Endpoints

Each antibot has its own subdomain, so interactions stay organized:

https://<vendor>.takionapi.tech      e.g. https://datadome.takionapi.tech

Different walls expect different parameters and return different tokens, so always check that vendor's page for the exact endpoint, request body, and response.

Authentication

Send your key one of two ways:

Header

x-api-key: TAKION_API_XXXXXXXX

Query parameter

?api_key=TAKION_API_XXXXXXXX

Browser Details

Our solutions are not browser-based, but they read the headers you send to build a realistic fingerprint:

• User-Agent

• Sec-Ch-Ua

• Accept-Language

Providing accurate browser headers based on your produces more realistic tokens. If you send none, the latest chrome versions on MacOS will be used, but matching the headers you will send on the final request is strongly recommended.

Plan Details and Status

Check your key's status two ways:

• Use your Dashboard

• Send GET /plan on any Aantibot subdomain for a JSON response with your plan details

Get plan status

get

Returns the current status of the authenticated API key — plan name, request usage against your quota, and validity. Use it to monitor consumption in real time.

Authorizations

ApiKeyHeaderApiKeyQuery

x-api-keystringRequired

Responses

200

Plan details for the authenticated key.

application/json

Your plan details. The field names below are representative — confirm them against a live /plan response and adjust before publishing.

validbooleanOptional

Whether the key is currently active and within its limit.

Example: true

planstringOptional

The subscription tier name.

Example: Standard

requests_usedintegerOptional

Requests consumed in the current period.

Example: 12345

requests_limitintegerOptional

Total requests included in the current period.

Example: 100000

resets_atstring · date-time · nullableOptional

When the usage counter resets (null for non-cyclic plans).

Example: 2026-08-01T00:00:00Z

Other propertiesanyOptional

401

Invalid API key — the key is wrong, expired, or over its request limit.

application/json

get/plan

HTTPcURLJavaScriptPython

GET /plan HTTP/1.1
Host: datadome.takionapi.tech
x-api-key: YOUR_API_KEY
Accept: */*

{
  "valid": true,
  "plan": "Standard",
  "requests_used": 12345,
  "requests_limit": 100000,
  "resets_at": "2026-08-01T00:00:00Z",
  "ANY_ADDITIONAL_PROPERTY": "anything"
}

Error Codes

• 400 - Invalid Input Parameters: Review the data provided; there’s an issue with it.

• 401 - Invalid API Key: The API key is invalid, expired, or the request limit has been exceeded.

• 500 - Internal Server Error: Something unexpected occurred on our end. Contact us for support.