Kasada API
Kasada tokens,
without a browser.
Generate x-kpsdk-ct and x-kpsdk-cd payloads from the ips.js script via one reviewed API, for approved ticketing, retail, AI, and QA workflows. It uses the same API key as Akamai Web and BMP.
CT payload
CD proof-of-work
script ingestion
What it replaces
Kasada without a Chromium fleet.
Kasada-protected catalogs and ticketing inventory normally force a headless browser per check. Roolink turns the CT and CD steps into request-based calls your workers make directly.
Request-based integration
Call CT and CD endpoints from workers, agents, and pipelines without a browser stack.
One platform key
Same x-api-key and billing balance as Akamai Web and Akamai BMP.
Production fit
Built for repeat jobs where consistency, observability, and support matter.
Reviewed access
Manual use-case review for legitimate collection, validation, and research.
Common use cases
- Protected catalog and inventory monitoring
- Ticketing and event availability workflows
- Retail and sneaker drop research
- AI agents reaching Kasada-protected targets
- QA and synthetic checks on Kasada paths
Supported outputs
- x-kpsdk-ct payload generation
- x-kpsdk-cd proof-of-work
- ips.js script ingestion
- Request-ready token output
How it works
CT, then CD.
Send the ips.js script and request context to the CT endpoint for the initial token, then post the CD challenge fields for the proof-of-work response.
- POST ksd.roolink.io/api/v1/payload
- POST ksd.roolink.io/api/v1/cd
# CT: initial token from the ips.js script
curl -s https://ksd.roolink.io/api/v1/payload \
-H "x-api-key: $ROOLINK_KEY" \
-H "content-type: application/json" \
-d '{ "script": "<ips.js>", "ipsUrl": "...",
"language": "en-US",
"referer": "https://example.com/",
"userAgent": "..." }'
# CD: proof-of-work response
curl -s https://ksd.roolink.io/api/v1/cd \
-H "x-api-key: $ROOLINK_KEY" \
-H "content-type: application/json" \
-d '{ "st": 1769360294000, "ct": "...",
"fc": "", "domain": "example.com" }'FAQ
Kasada API questions.
What is the Kasada API?
Roolink's Kasada product generates the x-kpsdk-ct and x-kpsdk-cd payloads Kasada expects from the ips.js script, so approved teams can reach Kasada-protected endpoints with plain HTTP requests instead of a headless browser fleet.
Is Kasada generally available?
Yes. Kasada is generally available on the same plans and pay-as-you-go balance as Akamai Web and BMP, with the same use-case review for every account. Proof-of-work (x-kpsdk-cd) requests are free.
Is this a Kasada bypass marketplace?
No. Roolink is not a generic bypass marketplace. Every account goes through a manual use-case review and access is intended for legitimate data collection, validation, monitoring, and research.
How does it integrate with my stack?
Send the ips.js script, its URL, the page referer, your user agent, and your Accept-Language to the CT endpoint, and the CD challenge fields to the CD endpoint. It uses the same x-api-key as Akamai Web and BMP.
Ready to test Kasada?
Create an account, review pricing, or talk to us about a high-volume workflow.