Getting started

1. Store your credentials

Keep the API key and proxy on your backend:

export EVADE_API_KEY="evde_REPLACE_ME"

See authentication for scopes and quotas.

2. Start a solve session

curl --request POST \
  --url "https://api.evade.now/solve" \
  --header "authorization: Bearer $EVADE_API_KEY" \
  --header 'content-type: application/json' \
  --data '{
    "task": "shape",
    "proxy": "http://username:password@proxy.example:8080",
    "target_url": "https://www.southwest.com/air/booking/select-depart.html",
    "shape_js_url": "https://www.southwest.com/assets/app/scripts/swa-common.js",
    "target_api": "https://www.southwest.com/api/air-booking/v1/air-booking/page/air/booking/shopping",
    "target_api_method": "POST",
    "referer": "https://www.southwest.com/",
    "time_zone": "America/Los_Angeles",
    "retain_session": true
  }'

The proxy supports http, https, socks4, and socks5. time_zone must be a valid IANA name that matches the proxy exit region. retain_session: true keeps the generated challenge state available for the follow-up request in step 5. Omit it when you need only one protected request.

ua is optional. When omitted, Evade selects a browser identity from its pool and returns it as user_agent. Known page profiles are inferred from target_url.

3. Read the response

{
  "success": true,
  "headers": {
    "Accept": "application/json",
    "challenge-prefix-a": "generated-value",
    "challenge-prefix-b": "generated-value"
  },
  "user_agent": "Mozilla/5.0 (...the browser identity Evade selected...)",
  "session_id": "0123456789abcdef0123456789abcdef",
  "timings": {
    "network_ms": 1284,
    "other_ms": 412
  }
}

network_ms is time spent fetching the page, loader, and challenge. other_ms covers the remaining solve work.

4. Replay the request

Send the application request yourself through the same proxy. Copy every entry from headers, use user_agent unchanged, and preserve the destination method, URL, body, and cookies. Add your application-specific headers without replacing any header returned by Evade.

Do not merge values from multiple solves or reuse a generated header set for a different proxy, URL, method, body, browser identity, or session.

5. Generate follow-up headers

curl --request POST \
  --url "https://api.evade.now/solve" \
  --header "authorization: Bearer $EVADE_API_KEY" \
  --header 'content-type: application/json' \
  --data '{
    "task": "shape",
    "session_id": "0123456789abcdef0123456789abcdef",
    "target_api": "https://www.southwest.com/api/air-booking/v1/air-booking/page/air/booking/shopping",
    "target_api_method": "POST"
  }'

See session reuse before forwarding cookies from a completed application request into a continuation solve.

Overview

Shape

DataDome

Getting started

1. Store your credentials

2. Start a solve session

3. Read the response

4. Replay the request

5. Generate follow-up headers

​1. Store your credentials

​2. Start a solve session

​3. Read the response

​4. Replay the request

​5. Generate follow-up headers

1. Store your credentials

2. Start a solve session

3. Read the response

4. Replay the request

5. Generate follow-up headers