Browser endpoints
Endpoints your visitors' browsers call directly for forms, the chatbot and page-view counts.
These endpoints take no token. Atlas accepts a request only when its Origin header is your environment’s registered website origin; anything else gets 403 ORIGIN_DENIED. CORS is limited to that origin.
https://<delivery host>/v1/public/environments/{environmentId}| Method and path | Purpose |
|---|---|
GET /forms/{formKey} |
Form definition, settings and the challenge to show |
POST /forms/{formKey}/submissions |
Submit. See Forms and leads for the body |
Chatbot
Section titled “Chatbot”| Method and path | Purpose |
|---|---|
GET /bots/{botKey} |
Appearance and triggers |
POST /bots/{botKey}/conversations |
Start: { path?, challengeToken? } → { conversationId, secret, messages } |
POST /bots/{botKey}/conversations/{id}/messages |
Send: { secret, text? (≤ 1,000 chars), choice?, challengeToken? } |
428 BOT_CHALLENGE_REQUIRED asks the browser to complete Turnstile and retry. 409 CONVERSATION_FULL after 80 messages. The chat widget handles all of this for you.
Page views
Section titled “Page views”POST /analytics/views with { "path": "/about" } returns 204. Send it after each page load and client-side navigation with fetch(…, { keepalive: true }). Skip previews and bots.
Atlas stores daily counts per route only: no cookies, no IP addresses, no visitor identifiers.