EverySolve CAPTCHA API
Imperva challenge API
EverySolve's Imperva challenge API returns cookie values for your challenge workflow. Send POST /api/v1/captcha with type set to imperva and the inputs listed below.
Imperva, historically called Incapsula, protects a page through browser and edge checks rather than a standalone image widget. It returns cookie data for the guarded workflow, not a widget token or a list of page resources.
- Endpoint
- POST /api/v1/captcha
- Type
- imperva
- Per 1,000 successful solutions
- $3.06 per 1,000 successful solutions
Request parameters
Provide website_url. Optional parameters are proxy and user_agent.
Required parameters
website_urlOptional parameters
proxyuser_agentcurl -X POST https://api.everyinfra.com/api/v1/captcha \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"type":"imperva","website_url":"<website_url>"}'
How to recognize Imperva challenge
Imperva, historically called Incapsula, protects a page through browser and edge checks rather than a standalone image widget.
What makes Imperva challenge different
It returns cookie data for the guarded workflow, not a widget token or a list of page resources.
Where the Imperva challenge parameters come from
website_url identifies the protected page; proxy and user_agent are optional but must match the session that consumes the cookie when used.
website_urlRequired- The exact page where this challenge appears, including the relevant path rather than only the site home page.
proxyOptional- 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.
What the API returns
The Imperva 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 Imperva challenge API
- 01Read GET /api/v1/captcha/types and select the
impervaentry. - 02Send
type: "imperva"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.
Imperva challenge integration questions
How can I identify Imperva challenge before choosing a type?
Imperva, historically called Incapsula, protects a page through browser and edge checks rather than a standalone image widget. Use imperva only after those signals match the target challenge.
Which target-page values belong in a Imperva challenge request?
website_url identifies the protected page; proxy and user_agent are optional but must match the session that consumes the cookie when used. Provide website_url. Optional parameters are proxy and user_agent.
What does Imperva challenge return, and what should not be confused with it?
The Imperva challenge API returns cookie values in cookie. Its solution format is cookie. It returns cookie data for the guarded workflow, not a widget token or a list of page resources.
Which external source explains the Imperva challenge integration?
Imperva's first-party Advanced Bot Protection page identifies the product family. [Open the Imperva challenge reference](https://www.imperva.com/products/advanced-bot-protection/). EverySolve-specific fields and live availability still come from the type catalog.