Send Transactional Message

Submit a request to send a single transactional message to a specific recipient. This endpoint is designed for high-reliability programmatic notifications.

How it works

Validation: The system validates your API Key and required scopes.

Routing: The recipient's number is analyzed to identify the target carrier network.

Pricing: Based on your organization's pricing plan, the cost for the specific route is calculated.

Funds Check: The system ensures your organization has sufficient credits. If so, they are reserved/debited.

Queuing: The message is placed in a high-priority delivery queue.

Response: A 202 Accepted status is returned with a unique message_id for tracking.

Limits

Rate Limit: This endpoint is limited to 15 requests per second per API Key.

Delivery Status

Since the delivery process is asynchronous, you should use the GET /messages/{message_id} endpoint or configure webhooks (if available) to monitor the message's progress.

curl --location --request POST 'https://dev.api.ziett.co/c/v1/messages' \ --header 'X-API-KEY: <api-key>' \ --header 'Content-Type: application/json' \ --data-raw '{ "channel_type": "SMS", "target_e164": "+244990090990", "content": "string", "save_contact": { "name": "string", "email": "user@example.com", "tags": [ "string" ] } }'

Send Transactional Message

How it works

Limits

Delivery Status

Request

Responses

Send Transactional Message

How it works#

Limits#

Delivery Status#

Request

Responses

How it works

Limits

Delivery Status