Skip to Content
AnySolver logo
AnySolver
Token

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

Wait for 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

ProviderPrice per 1,000Routing
RiskBypass
$1.00

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

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:

FieldTypeRequiredDescription
type*
Yes
secCpt*
stringYes

The initial sec_cpt value, from the response headers or the sec_cpt cookie of the 428 response.

Example: ADE36B02B21573BDBB5BFBF91F336959~1~....

secJson*
Record<string, unknown>Yes

The challenge JSON from the 428 response body, containing token, nonce, difficulty, count and timestamp among other fields.

Example: {"nonce":"30cc8a4637ca...","difficulty":5000,"token":"AAQAAAAL_____...","count":10,"timestamp":1758097163}

{
    "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

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.

token
stringNo

Challenge token to send together with answers, when the provider returns it.

Example: AAQAAAAL_____...

answers
string[]No

Computed proof-of-work answers. For the crypto provider, wait the challenge duration (chlg_duration), then post them with the challenge token to /_sec/verify?provider=crypto on the target domain.

Example: ["0.66463d05840cd"]