eSauti for developers
Start with an eSauti API key and the product access your workspace needs. These examples show the public API request shape; the API reference has the complete contract.
Open API reference ↗Pass your workspace API key as a Bearer token. Give it only the scopes needed by your integration. Keep the key on your server.
Authorization: Bearer <ESAUTI_API_KEY>01 / eSauti WhatsApp
Use a WhatsApp account configured for your workspace: an eSauti-hosted number provisioned by our team, or your own connected business account with the required product access. Use its account ID in the request. Confirm sender eligibility and messaging rules before sending.
curl https://api.esauti.com/v1/whatsapp/messages \
-H "Authorization: Bearer <ESAUTI_API_KEY>" \
-H "Idempotency-Key: <UNIQUE_SEND_ID>" \
-H "Content-Type: application/json" \
-d '{"account_id":"<YOUR_ACCOUNT_UUID>","type":"text","to":"+14165551234","text":"Hello from eSauti"}'Required scope: whatsapp:messages:send. Use a unique Idempotency-Key for each logical send; reuse it when retrying that send.
02 / eSauti Verify
Verify requires plan entitlement, an approved business display name, and active shared sender configuration. WhatsApp, SMS, and email are available.
curl https://api.esauti.com/v1/verify/verifications \
-H "Authorization: Bearer <ESAUTI_API_KEY>" \
-H "Idempotency-Key: <UNIQUE_VERIFICATION_ID>" \
-H "Content-Type: application/json" \
-d '{"recipient":"member@example.com","channel":"email","language":"en"}'Required scope: verify:write. Delivery starts asynchronously. The code is never returned by the create response.
Use the returned verification ID and the code entered by your customer to check the result.
curl https://api.esauti.com/v1/verify/verifications/<VERIFICATION_UUID>/check \
-H "Authorization: Bearer <ESAUTI_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"code":"123456"}'We can help with WhatsApp onboarding, Verify entitlement, sender approval, and the right API scopes.
Contact the eSauti team ↗