AkamaiSecCptToken
Solve the proof-of-work step of Akamai's sec-cpt challenge (HTTP 428) and get the answers to submit. Shows the request schema, an example and provider prices.
AkamaiSecCptToken computes the proof-of-work answers for Akamai's sec-cpt challenge, which you submit to the target domain. Akamai answers a request with HTTP 428 (Precondition Required) and a JSON body that starts with "sec-cp-challenge": "true". The provider field of that body selects the flow:
crypto: a proof-of-work with a mandatory wait.behavioral: only sensor data, as in the normal Akamai flow. It has no proof-of-work, so this task does not apply.adaptive: the proof-of-work first, then sensor data.
This task computes the answers for crypto and adaptive challenges. It is proxyless, because it works only from the values in the 428 response.
Collect the inputs
Pass the initial sec_cpt value (from the response headers or the sec_cpt cookie) as secCpt, and the challenge JSON from the response body as secJson. The JSON carries token, nonce, difficulty, count, timestamp and the wait duration chlg_duration.
Submit the answers
chlg_duration seconds. The server enforces the wait, and you cannot shorten it. Submit the answers right after the wait, before the challenge's timeout runs out.POST {"token": "<challenge token>", "answers": [<solution.answers>]} to /_sec/verify?provider=crypto on the
target domain. For an adaptive challenge, use provider=adaptive and send as many answers as the challenge
count.
For crypto and adaptive, finish with a GET to /_sec/cp_challenge/verify, then check the sec_cpt
cookie. A solved challenge sets a value that contains ~3~.
An adaptive challenge also needs a sensor step between the answers and the verification. Fetch the page at branding_cust_url, find the Akamai script on it, and post sensor data with AkamaiWebSensorProxyLess, stopping once the sec_cpt cookie is set.
Time-boxed
The challenge has a timeout (the timeout field of the JSON). Submit the answers promptly after the wait.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
RiskBypass | $1.00 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | Per-request settings for routing, Auto Retry, Auto Fallback, proxy reuse, response statistics and detailed analytics. Each field overrides the API key's value. See Routing modes. View settings reference |
Task Object Properties
The task field accepts an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
secCpt* | string | Yes | The initial Example: |
secJson* | Record<string, unknown> | Yes | The challenge JSON from the 428 response body, containing Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "AkamaiSecCptToken",
"secCpt": "ADE36B02B21573BDBB5BFBF91F336959~1~....",
"secJson": {
"nonce": "30cc8a4637ca...",
"difficulty": 5000,
"token": "AAQAAAAL_____...",
"count": 10,
"timestamp": 1758097163
}
}
}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
token | string | No | Challenge token to send together with Example: |
answers | string[] | No | Computed proof-of-work answers. For the Example: |