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.
The scriptID parsed from the page's HTML
Your session’s __cuid cookie, if available.
The browser's user-agent string to simulate during the request.
Client hints for content negotiation (used by some modern browsers).
Token generated
The generated or provided __cuid to be set in your session.
The generated x-castle-request-token for use in your next request.
Bad request, missing or invalid parameters
Internal server error
Last updated