Prepare hCaptcha enterprise token requests

Confirm enterprise access and supply the correct sitekey, URL, and rqdata rather than treating a regular token job as an enterprise equivalent.

Confirm access before changing the task type

Enterprise token tasks in easycaptcha require account approval. Contact sales through the contact form before relying on this task family in an application rollout. Changing a request’s type does not grant the permission required to submit it.

Keep the account entitlement separate from the challenge configuration. A permitted account can still send the wrong sitekey, URL, or request data. Diagnose admission errors and integration mismatches as different failures.

Supply enterprise-specific input

{
  "type": "hcaptcha_enterprise_token",
  "sitekey": "YOUR_SITEKEY",
  "url": "https://your-site.example/login",
  "rqdata": "YOUR_INTEGRATION_RQDATA",
  "hold": 30
}

rqdata belongs to the integration being evaluated. Do not reuse a placeholder or a value copied from an unrelated flow. Keep it associated with the exact challenge context that requested the token.

The request still uses the customer API key in the Authorization header. Enterprise data is not a substitute for authentication, and it should not be confused with the site owner’s verification secret.

Observe the same lifecycle

Create once, retain the task ID, and retrieve queued or running work until it reaches a terminal state. A completed enterprise token job exposes its token through the token result shape. A failed job carries an embedded error even when retrieval succeeds at the HTTP layer.

If a local deadline ends, preserve the ID for recovery. Automatically sending new enterprise jobs because the previous request was slow can produce additional paid work and make the evaluation harder to reconcile.

Compare enterprise work in its own cohort

Use the enterprise price and any selected mode multiplier when estimating cost. Do not infer enterprise behavior from a successful regular-token demo. Test the actual configuration with required request data and record observed acceptance separately from solver completion.

See regular versus enterprise tokens for the scope distinction, worker proxies for optional network input, and token API examples for the complete submission and polling flow.