---
title: "SMS consent setups"
description: "Where and how people opt in to your texts; a messaging program points at one."
url: https://www.unitpost.com/docs/api/sms-consent-setups
section: API reference
updated: 2026-10-13
---
# SMS consent setups

## SMS consent setups

> Where and how people opt in to your texts; a messaging program points at one.

Full schemas: [OpenAPI 3.1](https://www.unitpost.com/api/v1/openapi.json). HTML reference: https://www.unitpost.com/docs/sms#sms-consent-setups.

## Operations

### `GET /api/v1/sms/consent-setups`

List consent setups

Where and how people opt in to your texts: the form or page, the brand and purpose it discloses. A messaging program points at one with `consent_setup_id`. Archived ones are left out. Requires the `sms:read` capability.

Reference: https://www.unitpost.com/docs/sms/get-sms-consent-setups ([Markdown](https://www.unitpost.com/docs/sms/get-sms-consent-setups.md))

## Related

- [SMS test numbers](https://www.unitpost.com/docs/api/sms-test-numbers): The numbers a template's test text may go to besides the simulator. Adding and verifying one happens in the dashboard (a code is texted to the phone).
- [SMS registrations](https://www.unitpost.com/docs/api/sms-registrations): Carrier registrations and their review state. Submitting a 10DLC one is an SMS quote, then its confirm.
- [SMS billing](https://www.unitpost.com/docs/api/sms-billing): What your workspace pays for SMS every month. Buying a carrier resource is an SMS quote, then its confirm.