Skip to Content
AnySolver logo
AnySolver
Token

ShapeF5Token

Generate the Shape (F5) request headers through your own proxy for a protected API call such as login, search or checkout.

ShapeF5Token produces the Shape (F5) request headers for one call to a protected API, through your proxy, and returns them as a header map in solution.headers. Shape protects individual API calls rather than whole pages: the Shape script on the page computes a set of request headers, and the API rejects a call that does not carry them.

Use your proxy

task.proxy is required on this task type, and the provider solves from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Send the protected request from the same address, with the same User-Agent.

Find the parameters

Open the page that makes the protected call with DevTools and the Network tab:

  • targetUrl is the URL of the page that sends the call, and title is that page's document.title.
  • targetApi is the full URL of the protected request, and method is its HTTP method (GET or POST).
  • shapeJsUrl is the Shape script. Find the script request that has seed= in its URL; the script request before it is the Shape script.
  • referer is the Referer the page sends with the call. Leave it out when targetUrl is the homepage.

Use the headers

Add every header in solution.headers to your request to targetApi. The headers are generated for the targetApi, method and page you sent. Create a new task when the call changes, and send the request soon after the task completes.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
RiskBypass
$2.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
targetUrl*
URLYes

URL of the page that sends the request to the protected API.

Example: https://example.com/login/

targetApi*
URLYes

URL of the protected API request (for example a login, search or order endpoint) that needs Shape headers.

Example: https://example.com/api/login

shapeJsUrl*
URLYes

URL of the Shape (F5) script the page loads. In the Network tab, find the script request that has seed= in its URL; the script request before it is the Shape script.

Example: https://example.com/shape-script.js

title*
stringYes

Title of the page at targetUrl (document.title).

Example: Log in

method*
Yes

HTTP method of the request to targetApi.

Example: POST

proxy*
string | objectYes

Proxy the provider solves through, as a string or an object. See Proxy configuration.

View proxy configuration

Example: http://user:pass@1.2.3.4:8080

referer
URLNo

Referer the page sends with the request to targetApi. Omit it when targetUrl is the homepage.

Example: https://example.com/

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "ShapeF5Token",
        "targetUrl": "https://example.com/login/",
        "targetApi": "https://example.com/api/login",
        "shapeJsUrl": "https://example.com/shape-script.js",
        "title": "Log in",
        "method": "POST",
        "proxy": "http://user:pass@1.2.3.4:8080"
    }
}

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
headers*
Record<string, unknown>Yes

Headers the provider returns for the request to targetApi, as a name to value map. Send all of them with that request, from the same IP and User-Agent.

Example: {"Cookie":"name=value...","User-Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36"}

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.