Bring Imperva verification into your access workflow

Integrate supported Imperva / Incapsula Cloud WAF verification workflows through an API. Test compatibility and maintain consistent IPs, headers and sessions.

Cookies and headers

Preserve cookies and matching User-Agent values. Avoid reusing a result with unrelated request contexts.

HTML or JSON validation

Check the content type and expected fields. HTTP 200 may still contain a verification or error page.

Start free trial API documentation Code generator
Illustrative request-context and API-routing flow

Core products & integrations

Challenge handling, proxy routing and AI tool integrations.

Handle JS Challenge, Turnstile and WAF session checks while keeping your existing scraper and parser.

  • JS Challenge · Turnstile
  • Consistent sessions and request profiles
Explore product

Use the API in AI coding tools, terminal tasks and workflows. Choose the integration that fits your tool.

  • Coding toolsCursor · VS Code · Cline
  • Terminal agentsClaude Code · Codex · OpenClaw
  • Workflowsn8n · Dify
Choose an integration
AI coding tools, terminal and workflows connected to an API
  1. Configure requests

    Set the target, parameters and proxy

  2. Verify & route

    Handle challenges and select the route

  3. Retrieve HTML / JSON

    Check response status and content

  4. Parse business data

    Extract data with your existing parser

Add Imperva verification to your existing application

Add Imperva verification to your existing application

Use the API for verification and request forwarding on supported Imperva / Incapsula targets. Keep your current collection system: confirm compatibility, then pass the response to your application.

  • Supported Imperva workflows

    Handle verified compatible targets; a proxy connection alone is not a verification service.

  • Keep HTTP request methods

    Forward GET, POST and other requests with their URL paths, query parameters and business bodies.

  • Custom headers and cookies

    Supply Referer, cookies and required headers to preserve the request context.

  • Configure browser fingerprints

    Choose browser and platform fingerprints according to the API documentation and keep parameters consistent.

  • Bring your own proxy

    Configure HTTP or SOCKS5 routing and choose an exit and session duration suited to the target.

  • Continue parsing HTML / JSON

    Use your existing parser after checking that the returned content matches the expected result.

Get API access

Integrate with the language your team already uses

Keep your development stack and collection framework with standard HTTP requests. Official SDKs are available for Python, Node.js and Go; other languages can call the documented API directly.

  • Python SDK

    Configure the API key, target and request parameters in your existing Python data-processing scripts.

  • Node.js SDK

    Call the API from services or scheduled jobs while retaining your asynchronous processing logic.

  • Go SDK

    Add API requests to Go services and use your business queue to schedule tasks and concurrency.

  • cURL examples

    Test the target, API key and proxy with a minimal request before moving working parameters into code.

  • Java HTTP integration

    Send requests with your existing HTTP client without replacing the application framework.

  • TypeScript HTTP calls

    Organize request parameters and response types in the HTTP client already used by your project.

Get API access
Integrate with the language your team already uses
Keep cookies, fingerprints and proxy sessions consistent

Keep cookies, fingerprints and proxy sessions consistent

Pagination and continuous access need a stable request context. With V2(s), combine Cookie or Part mode with a fixed or sticky proxy rather than changing the exit or browser parameters after verification.

  • Client-managed Cookie mode

    Store the encrypted cookies returned by the API and send them with later requests in the same task.

  • API-managed Part sessions

    Use x-cb-part to separate sessions while the API manages verification cookies for the target.

  • Isolate concurrent tasks

    Use different Parts for independent tasks or threads to avoid mixing verification contexts.

  • Fixed or sticky exits

    Configure the required fixed or time-limited proxy for V2(s) and keep its IP stable within a session.

  • HTTP / SOCKS5 proxies

    Bring custom routing through x-cb-proxy; proxy traffic and API credits are billed separately.

  • Matching browser fingerprints

    Configure x-cb-fp as documented and keep User-Agent, cookies and task context consistent.

Get API access

Validate the response before parsing or automation

A completed HTTP request does not necessarily contain business data. Use API status, target content and error information to decide what happens next, then pass valid results to your parser or automation.

  • Separate API and target status

    Read API status and target responses as documented rather than relying on a single HTTP code.

  • Check the content type

    Confirm the response is the expected HTML or JSON, not a challenge page or error message.

  • Validate HTML elements

    Look for expected page elements and data regions before running extraction logic.

  • Validate JSON fields

    Check fields, error flags and business status instead of treating empty or error objects as success.

  • Retain diagnostic details

    Keep returned request IDs, error codes and messages to reproduce issues and contact support.

  • Bound retries and waiting

    Limit retries by timeout and error type; stop when a target is unsupported or denies access.

Get API access
Validate the response before parsing or automation
Shape

Use Cases

Bring Imperva verification into your access workflow

E-commerce & Retail Data Collection

Monitor product listings, prices, stock, promotions and reviews across permitted retail sources.

Marketing & Advertising Data Collection

Track permitted ad creatives, landing-page changes and campaign signals for market research.

Social Media Data Collection

Monitor permitted public posts, engagement and sentiment for social listening and trend analysis.

Video & Image Asset Collection

Organize permitted media metadata and licensed assets into searchable reference libraries.

News & Publishing Data Collection (News / Fiction)

Collect permitted publication updates, topic pages and release information for research and monitoring.

Financial Market Data Collection (Stocks / FX / Crypto)

Collect permitted market prices, historical records and timestamps for research, alerts and analytics.

Jobs & Talent Data Collection

Monitor job listings, hiring demand, skills and salary ranges across permitted sources.

Real Estate & Local Services Data Collection

Track permitted property listings, local businesses and pricing changes for regional market research.

Travel, Visa & Ticketing Data Collection

Monitor permitted fares, availability and policy updates with dates, currency and region preserved.

Coupons & Promotions Data Collection

Track permitted offers, discount changes and expiry dates for campaign comparisons.

Logistics & Supply Chain Data Collection (Shipping / Vessels / Containers)

Monitor permitted schedules, container events and freight rates with shipment IDs and timestamps.

Security & Risk Intelligence Data Collection

Collect permitted public risk indicators and source evidence for review, scoring and alerts.

Scrapingbypass API Pricing

Test target compatibility, then choose an API plan for your usage




Billed monthly, ideal for short-term testing and smaller workloads
  • Basic Plan

  • $49

  •  Credits:
    80000
     Validity:
    30 Days
     Speed:
    20 req/s
  • Advanced Plan

  • $129

  •  Credits:
    1000000
     Validity:
    30 Days
     Speed:
    25 req/s
Recommended
  • Pro Plan

  • $259

  •  Credits:
    2200000
     Validity:
    30 Days
     Speed:
    25 req/s
  • Premium Plan

  • $489

  •  Credits:
    4600000
     Validity:
    30 Days
     Speed:
    30 req/s
    Best Value
  • Ultimate Plan

  • $1056

  •  Credits:
    12000000
     Validity:
    30 Days
     Speed:
    30 req/s




Scrapingbypass Onboarding Workflow

1.Create Your Account

Register a Scrapingbypass API account - Sign Up Now

Register a Scrapingbypass Proxy account - Sign Up Now

One account gives you API and proxy access. Log in within 30 days and open Trial Activity from the gift icon to claim trial credits and traffic.

2.Test with the Code Generator

Use the Code Generator to configure and test Imperva / Incapsula requests. Check target support in the API documentation and keep the proxy IP, cookies and session consistent.

V1 includes a rotating proxy. V2(s) requires a stable proxy IP; configure a sticky session of at least 10 minutes when using Scrapingbypass rotating proxies.

For assistance, see the API documentation or contact Scrapingbypass Support.

3.Integrate the Scrapingbypass API

Integrate your tested Imperva / Incapsula request code into the application. Validate response status and content before parsing, pagination or automation.

4.Select a Pricing Plan

After testing, choose an API-credit plan based on your usage. View Pricing

For proxy traffic, select a Rotating Datacenter or Rotating Residential proxy plan.

Challenge handling consumes API credits; some workflows also need a proxy. API credits and proxy traffic are billed separately. A proxy connection does not replace challenge handling.

Proxy extraction and sticky-session settings

Imperva API questions

Does a proxy replace verification handling?

No. A proxy provides routing. Verification handling must use the supported workflow for the target.

Proxy IP and region: Keep the same approved exit route during a session; rotate between independent tasks when appropriate.

Cookies and headers: Preserve cookies and matching User-Agent values. Avoid reusing a result with unrelated request contexts.

No universal support is promised. Confirm the target and challenge type with a small authorized test first.

No. Validate returned content before parsing, including the expected HTML or business fields.

HTML or JSON validation: Check the content type and expected fields. HTTP 200 may still contain a verification or error page.

Review the API documentation, confirm the target with support and check the applicable API and proxy plans.

V1 and V2(s) consume 1 API credit for each successful request.

When V2(s) successfully completes a verification challenge, it consumes 2 additional credits. This covers supported Cloudflare JS Challenge, Cloudflare Turnstile, DataDome and Incapsula challenges.

An unsuccessful request does not consume the base request credit. However, the 2 challenge credits are deducted as soon as verification succeeds and are not refunded if the subsequent response fails.

Credit consumption rules
Imperva API questions
User reviews of our Scrapingbypass products and services

Trusted by developers and data professionals worldwide

Scrapingbypass Help Center

API documentation · Code generator · API Tutorials

API documentation

API documentation

Keep the same approved exit route during a session; rotate between independent tasks when appropriate.

View More
Code generator

Code generator

Preserve cookies and matching User-Agent values. Avoid reusing a result with unrelated request contexts.

View More
API Tutorials

API Tutorials

Explore API integration tutorials, code examples and common questions covering request configuration, sessions and response validation.

View More