Bypass Solution

This documentation provides detailed information on generating the Castle x-castle-request-token.

How the Solution Works

To bypass Castle:

1. Parse the site key from the webpage (starts with pk_).

2. Send it along with your session’s __cuid (if you have one).

3. Parse the response and use the x-castle-request-token.

Required Parameters:

• sitekey: The site key from the webpage.

Optional Parameters:

• __cuid: The session’s __cuid cookie. If not provided, one will be generated.

It's highly recommended to provide your session’s User-Agent, Sec-Ch-Ua, and Accept-Language headers for more accurate token generation.

Example Response

{
  "__cuid": "...",  // Set this on your session if not provided
  "x-castle-request-token": "..."  // Use this token for your next request
}

In order to access any of our endpoint you'll need a valid API Key, either join our discord for a trial or puchase a plan

Generate x-castle-request-token

This endpoint generates the x-castle-request-token for Castle-protected websites. It requires the site key from the website, and optionally the __cuid cookie from your session. The browser's user-agent string and client hints can also be passed for content negotiation.

GEThttps://castle.takionapi.tech/generate

Query parameters

Header parameters

Response

200400500

Token generated

Body

application/json

__cuidstring

The generated or provided __cuid to be set in your session.

x-castle-request-tokenstring

The generated x-castle-request-token for use in your next request.

Request

JavaScriptCurlPython

const response = await fetch('https://castle.takionapi.tech/generate', {
    method: 'GET',
    headers: {},
});
const data = await response.json();

Response

200400500

{
  "__cuid": "text",
  "x-castle-request-token": "text"
}