> For the complete documentation index, see [llms.txt](https://docs.vsat.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vsat.dev/readme.md).

# Introduction

> Request-based DataDome solver. Fetch the challenge your target served, send it here, and replay the returned payload from your own transport, using the same User-Agent, TLS fingerprint, IP, and header order for the whole flow. No headless browser, no per-solve cold start.

**Base URL:** `https://api.vsat.dev`

## Endpoints

| method | path            | solves                                        |
| ------ | --------------- | --------------------------------------------- |
| POST   | `/interstitial` | interstitial device check (`rt:'i'`)          |
| POST   | `/slider`       | slider captcha, `noPuzzle` variant (`rt:'c'`) |
| POST   | `/tags`         | tags telemetry (POST to the target's `/js`)   |
| GET    | `/health`       | readiness (no auth)                           |

Every POST body is `application/json`; every route except `/health` needs a bearer token. Responses share a common [envelope](/reference/envelope.md).

{% hint style="info" %}
️ Caller-supplied challenge code is executed in an isolated, authenticated sandbox and never reaches the host process.
{% endhint %}

## Quick start

```bash
curl -s https://api.vsat.dev/interstitial \
  -H "Authorization: Bearer $VSAT_TOKEN" \
  -H "content-type: application/json" \
  -d '{"userAgent":"...","deviceLink":"https://geo.captcha-delivery.com/interstitial/?...","html":"<the page you GET>"}'
```

New here? Read [Identify the challenge](/understanding-datadome/identify.md), then the endpoint for what you were served. Before going live, skim [Integration tips](/reference/tips.md).

Machine-readable: [OpenAPI spec](https://api.vsat.dev/openapi.json) · llms.txt


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vsat.dev/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.