> ## Documentation Index
> Fetch the complete documentation index at: https://docs.evade.now/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

> Solve DataDome tags, interstitial, and slider challenges with Evade.

DataDome has three flows: background **tags** telemetry, an automatic
**interstitial** device check, and an interactive **slider captcha**. Evade
generates the payload for each; your backend owns the target connection, proxy,
cookies, and final submission.

<Info>
  Send requests to `https://api.evade.now` and authenticate with your Evade
  bearer key. Every request body sets `"task": "datadome"`; each `POST /solve`
  body also sets a `mode` of `tags`, `interstitial`, or `captcha`.
</Info>

## The loop

<Steps>
  <Step title="Start the target session">
    Choose the exact User-Agent, locale, one sticky proxy, and one cookie jar,
    then make the protected request.
  </Step>

  <Step title="Classify the response">
    Route by `rt`, loader name, or device URL path — not the status code alone.
  </Step>

  <Step title="Generate with Evade">
    Call `POST /solve` with the matching `tags`, `interstitial`, or `captcha`
    mode. On the first solve, send `user_agent`, `accept_language`, and the
    target connection's public `ip`. Evade resolves timezone and country from
    MaxMind, derives the browser's ordered language list, and returns an
    opaque `session_id`; send only that identity on later solves. For an
    interstitial, also send its final URL as `device_link`, its exact response
    body as `html`, and the exact external bundle body as singular `script`
    only when the HTML references one.
  </Step>

  <Step title="Submit and install the cookie">
    Send Evade's output through your target client, replace the `datadome`
    cookie in the same jar, and retry the protected request.
  </Step>
</Steps>

Keep the proxy, public IP, User-Agent, cookie jar, and locale consistent for the whole
session — a generated payload describes that exact context, not a standalone
token.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.