Bypass Solution
This documentation provides detailed information on generating the Castle x-castle-request-token.
How the Solution Works
Required Parameters:
Optional Parameters:
Example Response
{
"__cuid": "...", // Set this on your session if not provided
"castle": "..." // Use this token for your next request
}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.
Authorizations
x-api-keystringRequired
Query parameters
scriptIDstringRequired
The scriptID parsed from the page's HTML
__cuidstringOptional
Your session’s __cuid cookie, if available.
Header parameters
User-AgentstringOptional
The browser's user-agent string to simulate during the request.
Sec-Ch-UastringOptional
Client hints for content negotiation (used by some modern browsers).
Responses
200
Token generated
application/json
400
Bad request, missing or invalid parameters
application/json
500
Internal server error
application/json
get
/generateLast updated