Skip to main content
Follow one appointment reminder from API availability to recipient-level delivery. The same ClientReference connects the send request to the delivery receipt (DLR).
Campaign creation uses the live messaging service and can consume message credits. Send only to recipients you are permitted to message and use a Sender ID approved for your account.

​
Before you begin

You need:

Check API health

The health endpoint is public:
Check health
A 200 OK response containing Healthy confirms that the API is responding at that moment.

Send one SMS

Submit one recipient with a Client Reference from your system:
Create campaign
The API returns 202 Accepted with a campaign UUID:
Campaign accepted
Store the UUID with the record that initiated the send. Acceptance means the campaign is queued; it does not mean the handset received the message.

Read campaign totals

Request the campaign summary with the returned UUID:
Get campaign summary
Campaign summary
A new campaign can return 404 Not Found before its summary is ready. Retry with backoff when you have just received the campaign UUID.

Receive the delivery receipt

Phonovation posts the recipient-level result to your configured webhook:
Delivered DLR
Verify X-Signature against the exact raw request bytes before parsing the JSON. Use ClientReference to locate appointment-88421, apply the DLR’s Status, and return a 2xx response after storing or queueing the event.
The campaign UUID tracks aggregate totals. ClientReference tracks the individual recipient through the webhook.

​
Go deeper

Connect the MCP server

Search the guides and API Reference directly from a compatible coding assistant.

Authentication

Compare personal access tokens with the optional OAuth lifecycle.

Sending SMS

Learn encoding, scheduling, recipient validation, and partial processing.

Webhooks

Implement signature verification, acknowledgements, and retries.