Skip to content

Use code FUN10 for 10% bonus credits

DocsAkamai (sec_cpt)

Akamai sec_cpt API Reference

Solve Akamai sec_cpt proof-of-work challenges and replay the cookies.

Read Markdown (English)

The Captcha.fun Akamai (sec_cpt) API accepts kind, url and returns sec_cpt cookies. Send the API_KEY header, create a solve with POST /v1/request, then poll GET /v2/response/{id} until ready is true.

What you’ll need

  • Your API key
  • The URL of the page where the challenge appears
  • Optional: triggerUrl, triggerBodyJson, protectedUrl
  • A proxy, if the result must come from your own IP (akamai_sec_cpt_proxy)
Use kind

Good to Know

The Akamai sec_cpt product solves the 428 sec-cp-challenge proof-of-work in a real browser: the solver triggers the challenge from the page context, works the proof, and returns the solved sec_cpt cookie plus any Akamai session siblings.

The trigger URL defaults per site; pass triggerUrl with an optional JSON body when your deployment's challenge fires on a specific API call. protectedUrl names the endpoint you will replay against (advisory — not a pre-return validation).

Send the Challenge

Send the page details with your API key. You get a solve id back right away.

POSThttps://api.captcha.fun/v1/request
curl -X POST https://api.captcha.fun/v1/request \
  -H "API_KEY: CAPFUN-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
  "kind": "akamai_sec_cpt",
  "url": "https://your-domain.example"
}'

Response

Returns the solve id. Use it to get the result.

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "message": "Started Solving"
}
Request fields7 body fields · 2 required

Headers

NameTypeRequiredDescription
API_KEYstringYesYour API key
Content-TypestringYesapplication/json
APP_IDstringNoOptional app ID for request tracking

Body

NameTypeRequiredDescription
kindstringYesOne of akamai_sec_cpt, akamai_sec_cpt_proxy
urlstringYesPage URL where the challenge appears
triggerUrlstringNoAPI URL whose 428 response triggers the challenge. Has per-site defaults
triggerBodyJsonstringNoRaw JSON body for the trigger request — paired with triggerUrl
protectedUrlstringNoEndpoint you will replay the session against. Defaults to url. Advisory — the solver does not validate against it before return
proxystringNoFor _proxy kinds: host:port or host:port:username:password
platformstringNoRequested platform label: windows (default) or mac

Wait for the Result

Use the solve id to fetch the result.

GEThttps://api.captcha.fun/v2/response/{id}

Poll every second until ready is true.

Example

curl -X GET https://api.captcha.fun/v2/response/550e8400-e29b-41d4-a716-446655440000 \
  -H "API_KEY: CAPFUN-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
  -H "Accept: application/json"

Response

{
  "ready": true,
  "status": "SUCCESS",
  "success": true,
  "userAgent": "RETURNED_USER_AGENT",
  "secUa": "RETURNED_SEC_CH_UA",
  "token": "2B3C4D5E6F7G8H9I0J1K~0~...,",
  "cookies": {
    "sec_cpt": "2B3C4D5E6F7G8H9I0J1K~0~...,",
    "bm_sz": "bm-sz-sibling..."
  },
  "cookieHeader": "sec_cpt=2B3C4D5E6F7G8H9I0J1K~0~...,; bm_sz=bm-sz-sibling..."
}
Request and response fields9 response fields

Request

NameTypeRequiredDescription
idstring (UUID)YesPath parameter. The id from Create Solve
API_KEYstringYesHeader. Your API key

Response Fields

NameTypeRequiredDescription
readyboolean—true when the solve is finished (v2 only)
statusstring—PENDING while solving, then SUCCESS or FAILURE
successboolean—Whether the solve succeeded
userAgentstring—Value to send as User-Agent when using the result. Preserve it exactly
secUastring—Value to send as Sec-CH-UA when using the result
tokenstring—The solved sec_cpt cookie value
cookiesobject—The defense cookie family, cookie name to value
cookieHeaderstring—The solving session's full Cookie header value, verbatim — replay it with the returned userAgent from the same egress IP
messagestring—Failure reason. Omitted on success

Send the Cookies

Replay cookieHeader as the Cookie header on outbound requests, with the returned userAgent as your User-Agent header, from the same egress IP as the solve.

When using a successful result, preserve the returned userAgent as User-Agent and secUa as Sec-CH-UA.

Wrong or rejected result? Report the failed solve.

More from Akamai