Ziph documentation

Connect your WhatsApp number, send WhatsApp and SMS messages from your application, and inspect their delivery status.

Start here

Follow the quickstart to connect a number, create an API key, and send your first WhatsApp message.

Already integrating? Open the API Reference for endpoint definitions, request fields, and responses.

What you can build

CapabilityWhat it does
WhatsApp messagingSend text, images, buttons, and single-select lists through a connected number.
SMS messagingSend text using a separate segment allowance.
Message inspectionLook up submission records and available status history.
Inbound webhooksForward supported incoming WhatsApp messages and interactive replies to your application.

Use the dashboard to manage channels, API keys, messages, webhooks, and billing. The Templates page helps you build and copy message JSON; it does not save templates or send messages.

Choose a guide

  • Channels: pair your WhatsApp number and understand SMS requirements.
  • Messages: choose a format, retry safely, and interpret statuses.
  • Webhooks: receive incoming WhatsApp messages and verify signatures.
  • Billing: understand trial access, allowances, and payments.

Know the limits

Provider acceptance is not proof of delivery. WhatsApp delivery and read updates depend on the connected route; SMS delivery receipts are not currently available. Interactive WhatsApp messages may render differently across clients.

Inbound webhooks are best-effort, with no retry, replay, or inbound archive. Build your workflow around these limits rather than assuming every event will arrive.

Ziph keeps delivery records, not message bodies or full recipient numbers. Message responses show masked recipients; retain any application history you need in your own system.