Legacy Cloud API

Migrate to API v1

Path mapping from /external-api to the canonical /v1 surface. Existing clients can migrate endpoint by endpoint with no forced deadline.

Legacy CloudAPI v1
GET /external-api/ping (IP discovery) GET /v1/ping
GET /external-api/contact/list GET /v1/contacts
POST /external-api/contact/store POST /v1/contacts
POST /external-api/contact/update/{id} PATCH /v1/contacts/{id}
DELETE /external-api/contact/delete/{id} DELETE /v1/contacts/{id}
GET /external-api/inbox/conversation-list GET /v1/conversations
GET /external-api/inbox/conversation-messages/{id} GET /v1/conversations/{id}/messages
POST /external-api/inbox/send-message POST /v1/messages
GET /external-api/inbox/template-list GET /v1/templates
POST /external-api/inbox/send-template-message POST /v1/templates/send
Webhooks (register in dashboard) POST /v1/webhooks + delivery logs
Start here API v1 Getting Started → Authentication → Messages → Webhooks.