---
title: "Get a contact's SMS consent"
method: GET
path: "/contacts/{id}/sms-consent"
tags: ["SMS"]
---

# Get a contact's SMS consent

`GET /contacts/{id}/sms-consent`

## Request

- Base URL: `https://www.unitpost.com/api/v1`
- URL: `https://www.unitpost.com/api/v1/contacts/{id}/sms-consent`
- Auth: HTTP bearer

Read a contact's current SMS consent state and the full immutable consent history — what was agreed to, when, and from which source. Use this to answer a carrier or regulator asking you to prove a recipient opted in, without contacting support. `marketing_eligible` is the field that decides whether marketing SMS to this contact will be accepted. Requires the `contacts:read` capability.

## Response `200`

The consent state and history.

- SmsConsent
  - `object` 'sms_consent', required
  - `phone` string, nullable, required
  - `country` string, nullable
  - `status` string, required
  - `marketing_eligible` boolean
  - `consented_at` string, nullable
  - `consent_source` string, nullable
  - `consent_purpose` string, nullable
  - `history` object[], required
    - `id` string, required
    - `action` string, required
    - `source` string, nullable, required
    - `purpose` string, nullable, required
    - `occurred_at` string, required
    - `evidence_url` string, nullable, required
    - `disclosure_version` string, nullable, required

## Other responses

- `401`: Missing or invalid API key.
- `404`: Contact not found.

---

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