EverySolve CAPTCHA API
PerimeterX challenge API
EverySolve's PerimeterX challenge API returns cookie values for your challenge workflow. Send POST /api/v1/captcha with type set to perimeterx and the inputs listed below.
PerimeterX, now part of HUMAN Security, is a page-level application-protection flow rather than an embedded checkbox. It returns cookie passage for the protected session, not a form token or a property listing from a protected site.
- Endpoint
- POST /api/v1/captcha
- Type
- perimeterx
- Per 1,000 successful solutions
- $3.06 per 1,000 successful solutions
Request parameters
Provide website_url and proxy. Optional parameters are user_agent and website_key.
Required parameters
website_urlproxyOptional parameters
user_agentwebsite_keycurl -X POST https://api.everyinfra.com/api/v1/captcha \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"type":"perimeterx","website_url":"<website_url>","proxy":"<proxy>"}'
How to recognize PerimeterX challenge
PerimeterX, now part of HUMAN Security, is a page-level application-protection flow rather than an embedded checkbox.
What makes PerimeterX challenge different
It returns cookie passage for the protected session, not a form token or a property listing from a protected site.
Where the PerimeterX challenge parameters come from
Use website_url with the same proxy that will consume the result; user_agent and website_key apply only when the target exposes them.
website_urlRequired- The exact page where this challenge appears, including the relevant path rather than only the site home page.
proxyRequired- The proxy for the solve session; when a result is network-bound, use the same exit for the subsequent target request.
user_agentOptional- The browser user agent for this challenge session; keep it consistent when the returned result is bound to that session.
website_keyOptional- The public site or widget key copied from this exact target integration; it is not a secret key.
What the API returns
The PerimeterX challenge API returns cookie values in cookie. Its solution format is cookie. Attach the returned cookie fields to subsequent requests for the same workflow.
- Solution shape
- cookie
- Solution fields
cookie
How to use the PerimeterX challenge API
- 01Read GET /api/v1/captcha/types and select the
perimeterxentry. - 02Send
type: "perimeterx"and the required parameters to POST /api/v1/captcha. - 03Read cookie values from
cookie. - 04Attach the returned cookie fields to subsequent requests for the same workflow.
Billing and availability
EverySolve charges only when a solution is delivered successfully. Unsuccessful attempts are refunded automatically. Read available and the price fields from GET /api/v1/captcha/types at request time rather than treating them as static page content.
PerimeterX challenge integration questions
How can I identify PerimeterX challenge before choosing a type?
PerimeterX, now part of HUMAN Security, is a page-level application-protection flow rather than an embedded checkbox. Use perimeterx only after those signals match the target challenge.
Which target-page values belong in a PerimeterX challenge request?
Use website_url with the same proxy that will consume the result; user_agent and website_key apply only when the target exposes them. Provide website_url and proxy. Optional parameters are user_agent and website_key.
What does PerimeterX challenge return, and what should not be confused with it?
The PerimeterX challenge API returns cookie values in cookie. Its solution format is cookie. It returns cookie passage for the protected session, not a form token or a property listing from a protected site.
Which external source explains the PerimeterX challenge integration?
HUMAN Security's first-party documentation identifies the PerimeterX application-protection family. [Open the PerimeterX challenge reference](https://www.humansecurity.com/). EverySolve-specific fields and live availability still come from the type catalog.