API Reference
OIDC
Platform

Messaging Providers

AdminUpdated Sep 11, 2026

Messaging Providers

Backend API — secret key (Authorization: Bearer sk_…).

5 routes. Each row is one endpoint with its explanation, required scope, and whether it honours the Idempotency-Key header.

Method & path

Scope

Idem

Explanation

GET /v1/messaging_providers

messaging:read

Read the instance's BYOK email and SMS provider config: transport, from-address and which secret keys are set. Never returns a secret value.

PUT /v1/messaging_providers/email

messaging:write

Configure the email delivery provider (Resend/SES/SMTP/Brevo/Mailgun). The provider secret is write-only; an omitted secret keeps the stored one.

PUT /v1/messaging_providers/sms

messaging:write

Configure the SMS delivery provider (Twilio). The auth token is write-only.

DELETE /v1/messaging_providers/:channel

messaging:write

Remove the email or sms provider configuration for the instance.

POST /v1/messaging_providers/:channel/test

messaging:write

Send a clearly-marked test message to a destination to verify the configured email or SMS provider delivers, without triggering a real auth flow. Rate-limited; 422 when nothing is configured.

Was this page helpful?