Skip to Content
AnySolver logo
AnySolver
Token

ThreatMetrixToken

Run a ThreatMetrix device profile for a session ID through your own proxy and get the profiling cookies. With the schema, an example and provider prices.

ThreatMetrixToken runs the ThreatMetrix device profiling for the session ID you send, through your proxy, and returns the profiling cookies. ThreatMetrix profiles the visitor's browser with a script on the page, and the site later asks ThreatMetrix about the profile that belongs to a session ID. Running the profiling for your session ID makes the site find a profile for that session.

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. Submit to the site from the same address, and use the returned solution.userAgent for the requests that follow.

Find the parameters

Open the page with DevTools and the Network tab and look for the profiling script request, which has org_id and session_id query parameters, for example https://{host}/fp/tags.js?org_id=...&session_id=...:

  • orgId is the org_id value.
  • sessionId is the session_id value. The site generates it per session, so read it from the page or create it the same way the site does, and send the same value to the site afterwards.
  • customDomain is the host that serves the script, such as tm.example.com.
  • pageId is the page identifier the site sets for the profiling tag (the pageid of the profiling snippet).
  • title is the page's document.title.

Use the result

solution.sessionId is the session ID that was profiled. Submit that ID where the site expects its session ID, and set solution.cookies on the session.

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/login

orgId*
stringYes

ThreatMetrix organization ID: the org_id query parameter of the profiling script (.../fp/tags.js?org_id=...).

Example: abcd1234

pageId*
stringYes

ThreatMetrix page ID: the tag identifier the site uses for this page (the pageid of the profiling snippet).

Example: 1

sessionId*
stringYes

ThreatMetrix session ID the page profiles: the session_id query parameter of the profiling script. The site generates it per session, so the profile is tied to the id you send.

Example: 3029471b-4b25-41cd-8d78-46598448325e

customDomain*
stringYes

Domain the site loads the ThreatMetrix profiling script from: the host of the profiling script request, for example tm.example.com.

Example: tm.example.com

title*
stringYes

Title of the target page (document.title).

Example: Log in

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": "ThreatMetrixToken",
        "websiteURL": "https://example.com/login",
        "orgId": "abcd1234",
        "pageId": "1",
        "sessionId": "3029471b-4b25-41cd-8d78-46598448325e",
        "customDomain": "tm.example.com",
        "title": "Log in",
        "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
sessionId*
stringYes

The session ID that was profiled. Submit it where the site expects its session ID.

Example: 3029471b-4b25-41cd-8d78-46598448325e

cookies*
Record<string, unknown>Yes

Cookies set by the ThreatMetrix profiling session. Replay them with the same IP and User-Agent.

Example: {"thx_guid":"a1b2..."}

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.