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

# Authentication

## Authentication

Every read request is scoped by a **public token** in the URL path — there's no header-based auth, no API key management flow to speak of.

```
https://cdn.overflowcms.com/v1/pk_live_.../collections/blog/items
                             ──────────
                              your site's public token
```

### What it is

A per-site token, `pk_live_...`, generated when the site is created. It's **not a secret** — it's designed to sit in your Webflow page's rendered HTML source, the same trust model as an analytics measurement ID. Anyone who can view your page's source can already see it; that's fine, because it only grants read access to *that one site's published content*. It cannot read drafts, cannot write anything, and cannot reach any other site.

### Where to find it

On the site's dashboard page, and on every collection's **Integrate** tab (which also gives you the exact JSON endpoint URL and embed snippet for that collection, pre-filled with the token).

### Rotation

If a token needs to be rotated (e.g. you're decommissioning an old integration), a new token can be issued; requests against the previous one stop resolving once it's retired. There's no scoped/read-vs-write distinction on this token — it is inherently read-only by what the API in front of it exposes.


---

# 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.overflowcms.com/api-reference/authentication.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.
