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

# POST /tags

Generate a DataDome `tags` body for a supported tenant. Tags is proactive telemetry: you POST it to the target's own `/js` endpoint to raise the session's trust score. It never appears in a block page.

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

## Flow

1. From a browser's own `/js` POST, note the `ddk` (sitekey, **static per site**) and the tags `version`.
2. **POST /tags** with `type: "ch"`. POST the returned `payload` to the target's `/js` endpoint; keep the `datadome` cookie it sets.
3. **POST /tags** again with `type: "le"`, and POST that body to `/js` too.

DataDome expects both posts per page load (`ch` then `le`); take the `datadome` cookie from the first.

## Request

| field            | type   | required | meaning                                                      |
| ---------------- | ------ | -------- | ------------------------------------------------------------ |
| `userAgent`      | string | yes      | Chrome UA                                                    |
| `cid`            | string | yes      | the current `datadome` cookie (empty on the first ever call) |
| `ddk`            | string | yes      | the site's DataDome key (static per site)                    |
| `referer`        | string | yes      | the referer header for the `/js` POST                        |
| `type`           | string | yes      | `ch` on the first call, `le` on the second                   |
| `version`        | string | yes      | the tags version (e.g. `5.9.0`)                              |
| `acceptLanguage` | string | no       | first language of Accept-Language                            |
| `ip`             | string | no       | the IP used to post to the target                            |

{% hint style="info" %}
️ Only tenants we've onboarded are solved natively. For any other tenant the service falls back to a generic profile and results may be less reliable. Ask us to add a tenant you need.
{% 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/tags.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.