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:
forterJsUrlis the URL of the Forter script. Many sites serve it from their own domain.siteIdis 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
| Provider | Price per 1,000 | Routing |
|---|---|---|
RiskBypass | $3.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 | ||
websiteURL* | URL | Yes | Full URL of the page where the CAPTCHA is displayed. Example: |
forterJsUrl* | string | Yes | URL of the Forter JavaScript snippet the page loads. Sites often serve it from their own domain. Example: |
siteId* | string | Yes | Forter site ID the snippet is configured with for the target site. Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
{
"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
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 |
|---|---|---|---|
token* | string | Yes | The Forter token generated for the session. Send it where the site expects it, for example in the Example: |
userAgent* | string | Yes | User-Agent string used during solving. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |