TakionAPI
Start a TrialJoin our DiscordBuy a PlanDashboard
  • Takion API
  • Interacting with our APIs
  • Datadome
    • Bypass Solution
    • Example Implementations
    • Common Errors & Troubleshooting
  • Incapsula / Imperva
    • reese84 Bypass Solution
    • ___utmvc Bypass Solution
    • Example Implementations
    • Common Errors & Troubleshooting
  • Perimeter X Mobile
    • Bypass Solution
    • Example Implementations
  • GeeTest
    • v3 Bypass Solution
    • v4 Bypass Solution
    • Example Implementations
  • AWS Cognito
    • Bypass Solution
    • Example Implementations
  • Castle
    • Bypass Solution
    • Example Implementations
  • NuData
    • Bypass Solution
    • Example Implementations
  • Image-to-Text Captchas / OCR
    • Bypass Solution
    • Example Implementations
  • Frameworks & Modules
    • Adyen and riskData
    • Queue-IT Module
Powered by GitBook
On this page
  • What is Castle?
  • x-castle-request-token

Was this helpful?

Castle

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

PreviousExample ImplementationsNextBypass Solution

Last updated 4 months ago

Was this helpful?

What is Castle?

Castle is an anti-bot service designed to prevent automated attacks such as account takeovers, fake account creation, and policy-violating behaviors. It monitors browser characteristics, user behavior, and request patterns to detect malicious activity.

x-castle-request-token

When interacting with Castle-protected endpoints, you must include a valid x-castle-request-token. This token is generated using various browser-specific factors, including the __cuid cookie and other session details. Our API generates this token, making it easy to integrate with Castle-protected websites.

An example website using it is .

DailyPay
Page cover image