> ## Documentation Index
> Fetch the complete documentation index at: https://developers.conveyour.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Sending messages and reading the threads they belong to.

Messaging covers what you send to contacts — by SMS or email — and the conversations those messages live in. You can send to a single contact or to a whole group. It exists because reaching people is rarely a single send: a message becomes a thread, and the thread is what your team actually works from. These endpoints let an integration send, read that history back, and organise it.

## Conversations

Conversations are the messages exchanged with a contact and the threads those messages belong to, and a thread can be assigned to a team member to own. The two read endpoints differ: listing messages returns only what your team sent out, while the conversations endpoint returns the full back-and-forth including the contact's replies. They exist so a team can run business messaging together — off personal phone numbers, with the whole history in one place — rather than as one-off sends. See [Conversations](https://conveyour.com/help/conversations) in the Help Center.

| Method | Endpoint | What it does |
| - | - | - |
| `GET` | [`/api/messages`](/api-reference/messages/list-messages) | List messages |
| `GET` | [`/api/messages/{id}`](/api-reference/messages/get-a-message) | Get a message |
| `POST` | [`/api/messages`](/api-reference/messages/create-a-message) | Create a message |
| `PUT` | [`/api/messages/{id}`](/api-reference/messages/update-a-message) | Update a message |
| `GET` | [`/api/messages/conversations`](/api-reference/messages/list-conversations) | List conversations |
| `GET` | [`/api/messages/events`](/api-reference/messages/list-message-events) | List message events |
| `POST` | [`/api/messages/assignments`](/api-reference/messages/assign-a-message) | Assign a message |

## Tags

Tags categorise conversations so they can be filtered and reported on, and your team can be required to tag a thread before closing it. A tag is stored on the message record, which is why counts come back as `messages_count`. They exist so you can find and report on conversations by meaning rather than by date or sender. Note these are conversation tags — distinct from the plain-text tags stored on a contact. See [Conversations Settings](https://conveyour.com/help/conversations-settings) in the Help Center.

| Method | Endpoint | What it does |
| - | - | - |
| `GET` | [`/api/tags`](/api-reference/tags/list-tags) | List tags |
| `GET` | [`/api/tags/{id}`](/api-reference/tags/get-a-tag) | Get a tag |
| `POST` | [`/api/tags`](/api-reference/tags/create-a-tag) | Create a tag |
| `PUT` | [`/api/tags/{id}`](/api-reference/tags/update-a-tag) | Update a tag |
| `DELETE` | [`/api/tags/{id}`](/api-reference/tags/delete-a-tag) | Delete a tag |
| `GET` | [`/api/tags/schema`](/api-reference/tags/get-tag-schema) | Get tag schema |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.