🏯Castle Documentation
Welcome to the comprehensive guide for the Takion Castle API. This documentation provides in-depth information about our available endpoints, their respective parameters, and the responses you can
Understanding Castle
Castle is an antibot service that detect automated and human-originated account takeovers, fake accounts, and any behavior that violates a platform policies based on several factors.
x-castle-request-token
In order to interact with Castle protected endpoints, you wanna be sure to use a good ip, as well as an header called x-castle-request-token
. This token is called based on several browser specifics as well as the generation timestamp as well as the __cuid
cookie.
Our API
Currently, we provide a comprehensive API, specifically designed for those protected websites.
Those websites will have inside their pages html that will always start with "pk_", that's the sitekey.
Generate the header
Build x-castle-request-token
GET
https://takionapi.tech/castle
When interacting with our API you'll need to pass the sitekey of the website, as well as your session's __cuid
if you already have one.
The response of the API will contain the x-castle-request-token
to use (valid for few seconds only for one request) and the __cuid
that you wanna set on your session (if you haven't provided one, we'll generate one that you'll have to set).
Query Parameters
Name | Type | Description |
---|---|---|
api_key* | String | Your API key |
Headers
Name | Type | Description |
---|---|---|
x-api-key | String | Your API key if not passed in query |
Request Body
Name | Type | Description |
---|---|---|
sitekey* | String | The page text |
__cuid | String | Your session's __cuid cookie if u have one. |
Last updated