Skip to Content
AnySolver logo
AnySolver
Token

ForterToken

Generate the Forter token for a session through your proxy, using the site's Forter script and site ID. With the schema, an example and provider prices.

ForterToken runs the site's Forter snippet through your proxy and returns the token for the session. Forter's JavaScript snippet collects device and behaviour data on the page and creates a token that the site passes to Forter on the back end.

Find the parameters

Open the page with DevTools and the Network tab:

  • forterJsUrl is the URL of the Forter script. Many sites serve it from their own domain.
  • siteId is the site ID the snippet is configured with. Read it from the snippet on the page.

Send the proxy

task.proxy is required on this task type, and the token is generated from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Use the token from the same IP and the same User-Agent.

Use the token

Send solution.token where the site expects its Forter token, for example in the forterToken cookie, and use the returned solution.userAgent for the same session. If the provider does not return a User-Agent, solution.userAgent is an empty string.

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

Supported Providers

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

Full URL of the page where the CAPTCHA is displayed.

Example: https://example.com/checkout/

forterJsUrl*
stringYes

URL of the Forter JavaScript snippet the page loads. Sites often serve it from their own domain.

Example: https://example.com/js/forter.js

siteId*
stringYes

Forter site ID the snippet is configured with for the target site.

Example: YOUR_FORTER_SITE_ID

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

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "ForterToken",
        "websiteURL": "https://example.com/checkout/",
        "forterJsUrl": "https://example.com/js/forter.js",
        "siteId": "YOUR_FORTER_SITE_ID",
        "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
token*
stringYes

The Forter token generated for the session. Send it where the site expects it, for example in the forterToken cookie.

Example: a1b2c3d4e5f6...

userAgent*
stringYes

User-Agent string used during solving.

Example: 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.