---
title: "Send a chase message"
method: POST
path: "/v1/intakes/{id}/chase"
tags: ["Intakes"]
---

# Send a chase message

`POST /v1/intakes/{id}/chase`

## Request

- Base URL: `https://api.briefgate.dev`
- URL: `https://api.briefgate.dev/v1/intakes/{id}/chase`
- Auth: HTTP bearer

Manually trigger a chase message to the client via email. `channel: "sms"` is also accepted by the schema (it additionally requires the `sms` feature — Studio plan or above — plus SMS credits) but is not currently available on this deployment; see `features.sms` in GET /pricing.json. The chase engine also sends reminders automatically based on the `chase_schedule` set at intake creation. Rate limited to 1 manual chase per intake per hour and 20 per account per hour, independent of the automatic schedule and enforced for both session and API-key callers.

## Path parameters

- `id` string, required

## Request body

- SendChase
  - `channel` 'email' | 'sms'

## Response `200`

Chase message sent

- object
  - `channel` string
  - `sent_at` string, date-time

## Other responses

- `400`: Invalid request — malformed body or query parameters
- `401`: Missing or invalid API key
- `402`: SMS credits exhausted or plan upgrade required
- `403`: Authenticated but not allowed to perform this action
- `404`: Resource not found
- `422`: Validation error — the body shape is correct but values are invalid
- `429`: Rate limit exceeded

---

[API](https://skmtc.dev/briefgate/apis/briefgate-api.md) · [All operations](https://skmtc.dev/briefgate/apis/briefgate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/briefgate/apis/briefgate-api/revisions/b21afed4748b?raw)