Skip to main content

1. Create a solve session

Send the full browser and page context on the first request:
The proxy must be an absolute http, https, socks4, or socks5 URL. It may include credentials in the URL.
The user agent must identify a browser supported by Evade and have a complete stored fingerprint. Submit it exactly as it will appear on the replay request.

2. Read the response

Save session_id if you need headers for follow-up API calls from the same page and challenge context.

3. Replay the request

Send the destination request through the same proxy. Copy every entry from headers, and use user_agent unchanged.
Do not merge the generated values into a different browser session. The proxy, cookies, user agent, destination URL, and method are part of the solved context.

4. Generate follow-up headers

Reuse the returned session with only the next destination request:
See session reuse for lifecycle and validation behavior.

Embedded interstitials

Some protected pages return the Shape VM directly inside a one-time interstitial instead of loading a separate shape_js_url. Send the page URL as both target_url and target_api, omit shape_js_url, and include the cookies from the browser session that reached the page:
The response has "one_time": true and no session_id. Replay all returned headers immediately, once, with a GET to the exact same URL through the same proxy. A repeated interstitial requires a fresh /solve request.