# Replies

Replies to your emails come back to Sendocado, tied to the email they answer.

Replies to your emails come to Sendocado, are tied to the email they answer, and show in the Replies inbox, the API and your [webhooks](https://sendocado.com/docs/webhooks).

## How replies reach you

Campaign and broadcast emails go out with a Reply-To address on Sendocado’s inbound domain that is unique to each email. Nothing to set up: a reply lands in the right project, tied to the send, the contact, and the campaign or broadcast it answers.

Each project also has its own inbound address (`inbound_address` on the project). Mail sent straight to it is kept too, tied to the contact by the sender’s address.

Transactional email uses the `reply_to` you send, or the sender’s Reply-To, so those replies go to you directly.

## Stopping on reply

A campaign with `is_stopped_on_reply` takes a person out when they reply (exit reason `replied`). Automatic replies, like out-of-office messages, are marked `is_auto_reply` and never stop a campaign or count as unread.

## Reading replies

```sh List unread replies
curl "https://sendocado.com/api/v1/projects/$PROJECT_ID/replies?is_unread=true" \
  -H "Authorization: Bearer $SENDOCADO_API_KEY"
```

A reply’s detail has the full text and its attachments. `html_url` serves the HTML as plain text so it can never run in a browser; show it in a sandboxed frame. Mark a reply read with an update. Replies are kept for 12 months.

To act on replies as they arrive, subscribe a [webhook endpoint](https://sendocado.com/docs/webhooks) to `reply.received`.