Skip to main content
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 in the Help Center.

​
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 in the Help Center.