> 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/generic-dialogue-provider/messages-and-dialogues.md).

# Legacy combined API route

Preserve legacy Generic Dialogue Provider endpoint links and route to the canonical resource pages.

This compatibility page retains the combined route and its rendered endpoint headings. Use the canonical resource links below for current navigation; compact fragments from older links are not aliases for the rendered headings.

All endpoints on these pages require:

```http
Authorization: ******
```

## Common path parameters

| Parameter      | Type   | Required | Description                   |
| -------------- | ------ | -------- | ----------------------------- |
| `messageId`    | string | Yes      | Message ID in GUID format.    |
| `dialogueId`   | string | Yes      | Dialogue ID in GUID format.   |
| `attachmentId` | string | Yes      | Attachment ID in GUID format. |

## Common error behavior

Endpoint-specific tables list the defined status codes. Validation errors use the service validation response format. Some not-found and conflict responses forwarded from Dialogue Manager are wrapped as:

```json
{
  "error": "<raw response>"
}
```

## Resources

* [Messages](/developer-docs/generic-dialogue-provider/messages.md)
* [Dialogues](/developer-docs/generic-dialogue-provider/dialogues.md)
* [Attachments](/developer-docs/generic-dialogue-provider/attachments.md)

## POST /api/v1/message

See [Create a message](/developer-docs/generic-dialogue-provider/messages.md#post-api-v1-message).

## GET /api/v1/message/{messageId}

See [Retrieve a message](/developer-docs/generic-dialogue-provider/messages.md#get-api-v1-message-messageid).

## PATCH /api/v1/message/{messageId}

See [Update a message](/developer-docs/generic-dialogue-provider/messages.md#patch-api-v1-message-messageid).

## POST /api/v1/message/{messageId}/link

See [Link a message to a dialogue](/developer-docs/generic-dialogue-provider/messages.md#post-api-v1-message-messageid-link).

## POST /api/v1/dialogue

See [Create a dialogue](/developer-docs/generic-dialogue-provider/dialogues.md#post-api-v1-dialogue).

## GET /api/v1/dialogue/{dialogueId}

See [Retrieve a dialogue](/developer-docs/generic-dialogue-provider/dialogues.md#get-api-v1-dialogue-dialogueid).

## POST /api/v1/dialogue/{dialogueId}/connect

See [Connect a dialogue](/developer-docs/generic-dialogue-provider/dialogues.md#post-api-v1-dialogue-dialogueid-connect).

## POST /api/v1/dialogue/{dialogueId}/disconnect

See [Disconnect a dialogue](/developer-docs/generic-dialogue-provider/dialogues.md#post-api-v1-dialogue-dialogueid-disconnect).

## POST /api/v1/message/{messageId}/attachment

See [Upload an attachment](/developer-docs/generic-dialogue-provider/attachments.md#post-api-v1-message-messageid-attachment).

## GET /api/v1/message/{messageId}/attachment/{attachmentId}

See [Download an attachment](/developer-docs/generic-dialogue-provider/attachments.md#get-api-v1-message-messageid-attachment-attachmentid).

## DELETE /api/v1/message/{messageId}/attachment/{attachmentId}

See [Delete an attachment](/developer-docs/generic-dialogue-provider/attachments.md#delete-api-v1-message-messageid-attachment-attachmentid).

## Related topics

* [Authentication](/developer-docs/generic-dialogue-provider/authentication.md)
* [Event subscriptions and 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/generic-dialogue-provider/messages-and-dialogues.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.