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

# Developer docs

Developer guidance for WebChat events and the Generic Dialogue Provider API.

Use this section when you are implementing an integration with Dialogue Cloud Neo.

## Choose your path

| If you need to...                                                      | Start here                                                                                                                                                                                                                                                  |
| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Build a custom text-channel integration with Generic Dialogue Provider | Complete [Generic Dialogue Provider setup](/channels-integrations/text-channels/generic-dialogue-provider.md), then follow the [Generic Dialogue Provider API implementation path](/developer-docs/generic-dialogue-provider.md#implementation-quickstart). |
| Authenticate or work with Generic Dialogue Provider API tasks          | Use the [Generic Dialogue Provider API](/developer-docs/generic-dialogue-provider.md).                                                                                                                                                                      |
| Run website code during the WebChat loading sequence                   | Use [WebChat front-end events](/developer-docs/webchat-front-end-events.md).                                                                                                                                                                                |

## Generic Dialogue Provider implementation journey

Generic Dialogue Provider administration and API implementation have separate owners. Use this sequence to move between them without copying environment-specific values:

1. Complete provider enablement and UCC setup in [Channels & integrations](/channels-integrations/text-channels/generic-dialogue-provider.md).
2. Obtain credentials and environment-specific values from the administrator who owns the provider configuration in Channels & integrations; do not infer them from examples in Developer docs.
3. Follow [Authentication](/developer-docs/generic-dialogue-provider/authentication.md).
4. Follow the core API sequence: [create a dialogue](/developer-docs/generic-dialogue-provider/dialogues.md#post-api-v1-dialogue), [create a message](/developer-docs/generic-dialogue-provider/messages.md#post-api-v1-message), [link the message](/developer-docs/generic-dialogue-provider/messages.md#post-api-v1-message-messageid-link), [subscribe to events](/developer-docs/generic-dialogue-provider/events.md#post-api-v1-subscribe), and [connect the dialogue](/developer-docs/generic-dialogue-provider/dialogues.md#post-api-v1-dialogue-dialogueid-connect).
5. Add [attachments](/developer-docs/generic-dialogue-provider/attachments.md) where needed, then validate the provider and its [event callbacks](/developer-docs/generic-dialogue-provider/events.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/developer-docs/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.