Imperva API
Imperva tokens,
without a browser.
Generate Imperva reese84 tokens and ___utmvc cookies from the site's own scripts via one reviewed API, for approved travel, retail, ticketing, AI, and QA workflows. It uses the same API key as Akamai and Kasada.
token payload
cookie
proof-of-work
What it replaces
Imperva without a Chromium fleet.
Imperva-protected travel and retail sites normally force a headless browser per session. Roolink turns the Reese84 and ___utmvc steps into request-based calls your workers make directly.
Request-based integration
Call the Reese84 and ___utmvc endpoints from workers, agents, and pipelines without a browser stack.
One platform key
Same x-api-key and billing balance as Akamai Web, Akamai BMP, and Kasada.
Matches your browser
Each payload comes from a real Chrome device with your exact User-Agent, so the token matches your requests.
Reviewed access
Manual use-case review for legitimate collection, validation, and research.
Common use cases
- Airline and travel fare monitoring
- Retail catalog and price monitoring
- Ticketing and event availability workflows
- AI agents reaching Imperva-protected targets
- QA and synthetic checks on Incapsula paths
Supported outputs
- Reese84 submission payloads
- GPC proof-of-work solved in the same call
- ___utmvc cookie generation
- Payloads from real Chrome devices with your User-Agent
How it works
Build, then submit.
Send the Reese84 script and request context to the payload endpoint and post the JSON it returns to the site for the reese84 token. Sites that set the ___utmvc cookie get it from the UTMVC endpoint.
- POST imperva.roolink.io/api/v1/payload
- POST imperva.roolink.io/api/v1/utmvc
# Reese84: the submission to post to the site
curl -s https://imperva.roolink.io/api/v1/payload \
-H "x-api-key: $ROOLINK_KEY" \
-H "content-type: application/json" \
-d '{ "script": "<reese84 script>", "scriptUrl": "...",
"pageUrl": "https://example.com/",
"userAgent": "...", "language": "en-US,en;q=0.9",
"pow": "<GPC challenge, if any>" }'
# UTMVC: the ___utmvc cookie
curl -s https://imperva.roolink.io/api/v1/utmvc \
-H "x-api-key: $ROOLINK_KEY" \
-H "content-type: application/json" \
-d '{ "script": "<Incapsula script>",
"cookies": "incap_ses_...=...", "userAgent": "..." }'FAQ
Imperva API questions.
What is the Imperva API?
Roolink's Imperva product builds the Reese84 submission and the ___utmvc cookie that Imperva (formerly Incapsula) expects from a real browser, so approved teams can reach Imperva-protected sites with plain HTTP requests instead of a headless browser fleet.
Is Imperva generally available?
Yes. Imperva is generally available on the same monthly plans and pay-as-you-go balance as Akamai Web, BMP, and Kasada, with the same use-case review for every account.
Is this an Incapsula bypass marketplace?
No. Roolink is not a generic bypass marketplace. Every account goes through a manual use-case review and access is intended for legitimate data collection, validation, monitoring, and research.
How does it integrate with my stack?
Send the Reese84 script, its URL, the page URL, your User-Agent, and your Accept-Language to /payload, with the GPC challenge when the site sets one, then post the returned JSON to the site. For the ___utmvc cookie, send the Incapsula script and your session cookies to /utmvc. It uses the same x-api-key as every other product.
Which browsers does it emulate?
Each payload is built from a real Chrome device that visited a site recently with your exact User-Agent, so the token matches your requests. Send a current desktop Chrome User-Agent from Windows or macOS.
Ready to test Imperva?
Create an account, review pricing, or talk to us about a high-volume workflow.