EverySolve CAPTCHA API

Kasada challenge data API

EverySolve's Kasada challenge data API returns named solution fields for your challenge workflow. Send POST /api/v1/captcha with type set to kasada_cd and the inputs listed below.

Kasada challenge-data generation starts from structured platform_inputs rather than navigating a protected URL. It returns `x-kpsdk-cd` with associated `ct` and `st` values. Use `kasada` for the URL-and-proxy browser flow.

Start for free View the type catalog

Endpoint: POST /api/v1/captcha
Type: kasada_cd
Per 1,000 successful solutions: $1.53 per 1,000 successful solutions

Request parameters

Provide platform_inputs. Optional parameters are site, challenge_key, session_token, session_timestamp, and dynamic_config.

Required parameters

platform_inputs

Optional parameters

sitechallenge_keysession_tokensession_timestampdynamic_config

kasada_cd.sh

curl -X POST https://api.everyinfra.com/api/v1/captcha \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"kasada_cd","platform_inputs":"<platform_inputs>"}'

How to recognize Kasada challenge data

Kasada challenge-data generation starts from structured platform_inputs rather than navigating a protected URL.

What makes Kasada challenge data different

It returns x-kpsdk-cd with associated ct and st values. Use kasada for the URL-and-proxy browser flow.

Where the Kasada challenge data parameters come from

Keep platform_inputs intact; site, challenge_key, session_token, session_timestamp, and dynamic_config are optional only when supplied by the same challenge session.

platform_inputsRequired: The structured platform inputs captured from the active Kasada challenge.
siteOptional: The site identifier attached to the active structured challenge.
challenge_keyOptional: The challenge key from the active session; it is not interchangeable with a generic website key.
session_tokenOptional: The token supplied by the same active challenge session.
session_timestampOptional: The timestamp supplied by the same active challenge session.
dynamic_configOptional: Dynamic configuration captured from the same active challenge session.

What the API returns

The Kasada challenge data API returns named solution fields in x-kpsdk-cd, x-kpsdk-ct, and x-kpsdk-st. Its solution format is fields. Read the declared fields together; the target workflow may require the complete set.

Solution shape: fields
Solution fields: x-kpsdk-cdx-kpsdk-ctx-kpsdk-st

How to use the Kasada challenge data API

01Read GET /api/v1/captcha/types and select the kasada_cd entry.
02Send type: "kasada_cd" and the required parameters to POST /api/v1/captcha.
03Read named solution fields from x-kpsdk-cd, x-kpsdk-ct, and x-kpsdk-st.
04Read the declared fields together; the target workflow may require the complete set.

Billing and availability

EverySolve charges only when a solution is delivered successfully. Unsuccessful attempts are refunded automatically. Read available and the price fields from GET /api/v1/captcha/types at request time rather than treating them as static page content.

Kasada challenge data integration questions

How can I identify Kasada challenge data before choosing a type?

Kasada challenge-data generation starts from structured platform_inputs rather than navigating a protected URL. Use kasada_cd only after those signals match the target challenge.

Which target-page values belong in a Kasada challenge data request?

Keep platform_inputs intact; site, challenge_key, session_token, session_timestamp, and dynamic_config are optional only when supplied by the same challenge session. Provide platform_inputs. Optional parameters are site, challenge_key, session_token, session_timestamp, and dynamic_config.

What does Kasada challenge data return, and what should not be confused with it?

The Kasada challenge data API returns named solution fields in x-kpsdk-cd, x-kpsdk-ct, and x-kpsdk-st. Its solution format is fields. It returns x-kpsdk-cd with associated ct and st values. Use kasada for the URL-and-proxy browser flow.

Which external source explains the Kasada challenge data integration?

Kasada's first-party site identifies the protection family; this structured field contract remains EverySolve-specific. [Open the Kasada challenge data reference](https://www.kasada.io/). EverySolve-specific fields and live availability still come from the type catalog.