> 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/endpoints/slider.md).

# POST /slider

Solve a DataDome slider captcha (the simple `noPuzzle` variant: "slide to confirm", no image gap to find). You fetch the captcha page, hand over its HTML, and submit the returned payload to the check endpoint.

|            |                                           |
| ---------- | ----------------------------------------- |
| Endpoint   | `POST https://api.vsat.dev/slider`        |
| Auth       | `Authorization: Bearer <token>`           |
| Returns    | `{ ok, payload, plv3 }`                   |
| TypeScript | `vsat.slider({ userAgent, html, cid })`   |
| Python     | `vsat.slider(userAgent=…, html=…, cid=…)` |

## Flow

1. **GET the target** with your transport. A `403` + `dd={'rt':'c', cid, …}` is the challenge (it can also be chained after an interstitial).
2. **GET the captcha page** at `https://geo.captcha-delivery.com/captcha/?cid=…`. Save the HTML body.
3. **POST /slider** `{ userAgent, html, cid }` to this API. You get back `{ ok, payload, plv3 }`.
4. **Submit** the `payload` and `plv3` to `https://geo.captcha-delivery.com/captcha/check` with your transport. A `200 { cookie: "datadome=…" }` means cleared; a `403` is a rejection.
5. **GET the target** again with the fresh `datadome` cookie.

## Request

| field              | type   | required | meaning                                          |
| ------------------ | ------ | -------- | ------------------------------------------------ |
| `userAgent`        | string | yes      | the session User-Agent (Chrome)                  |
| `html`             | string | yes      | the `/captcha/` page body you GET in step 2      |
| `cid`              | string | no       | the live `cid` from the challenge                |
| `motion`           | array  | no       | a drag path; generated if omitted                |
| `allowUnsupported` | bool   | no       | solve a Windows slider anyway (default: refused) |

## Response

```json
{ "ok": true, "payload": "…", "plv3": "…" }
```

{% hint style="danger" %}
️ A **Windows** UA returns `422 unsupported_challenge`: Windows draws the cold-slider surface, which is exit-reputation gated (a real browser is hard-blocked there too) and not reliably solvable. Use a macOS UA, or set `allowUnsupported:true` to solve anyway and grade it yourself.
{% endhint %}


---

# 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/endpoints/slider.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.