Compliance
Consent records and Indian DLT registration for SMS traffic on TryVox.
Compliance
TryVox's Compliance API handles the bookkeeping that regulators expect:
- Consent ledger — append-only record of opt-ins and opt-outs by phone number, queryable per send.
- Indian DLT (Distributed Ledger Technology) — sender ID and template registration as required by TRAI for SMS into India.
When the Messaging API or Voice API places an outbound message or call, an internal validator checks the consent ledger and (for India) the DLT registration before egressing. Records you write here are read at send time — the API will not silently override a missing consent or DLT entry.
Endpoints
All compliance endpoints are mounted under /v1/compliance/... and authenticate with HTTP Basic.
| Method | Path | Purpose |
|---|---|---|
POST | /v1/compliance/consent | Record opt-in |
DELETE | /v1/compliance/consent | Record opt-out |
GET | /v1/compliance/consent | Check consent for a single number |
GET | /v1/compliance/consent/bulk | Bulk consent check |
POST | /v1/compliance/dlt/registrations | Register a DLT entity |
GET | /v1/compliance/dlt/registrations | List registrations |
GET | /v1/compliance/dlt/registrations/{id} | Get a registration |
PUT | /v1/compliance/dlt/registrations/{id} | Update |
DELETE | /v1/compliance/dlt/registrations/{id} | Delete |
POST | /v1/compliance/dlt/templates | Register a DLT template |
GET | /v1/compliance/dlt/templates | List templates |
GET | /v1/compliance/dlt/templates/{id} | Get a template |
PUT | /v1/compliance/dlt/templates/{id} | Update |
DELETE | /v1/compliance/dlt/templates/{id} | Delete |
What gets blocked
| Send type | What's checked |
|---|---|
| SMS to any destination | Consent record for the recipient phone_number if you've enabled the consent gate on the channel. |
| SMS to +91 (India) | DLT registration with a matching sender_id, AND a DLT template whose template_body matches the outgoing message text. |
| Channel-level Meta consent (see Messaging Channels). The Compliance consent ledger is not checked for WhatsApp by default. | |
| Voice | Not gated by these endpoints. Voice consent is your application's responsibility (see Recordings → Compliance and consent). |
Pages
- Consent ledger — opt-in / opt-out / check / bulk check
- Indian DLT — registrations and templates
Notes
- Consent records are append-only. Recording an opt-out doesn't delete the prior opt-in; both events stay in the ledger and the latest event wins on
Check. - DLT records mirror, not replace. TryVox stores your DLT entity and template metadata so the Messaging API can validate sends — this does not register you with the DLT operator. You still need to register through Jio TrueConnect / Airtel / VI / BSNL portals as usual.
- Tenant scope is automatic. All compliance records are tenant-scoped via the API key's tenant; you don't pass a tenant ID in the URL.