Legacy docs

These APIs are no longer maintained

For new integrations, use the current EZ Texting API. To move an existing integration, see the Legacy migration guide.

EZ Texting has offered several APIs over the years. This section preserves the documentation for the legacy APIs so that existing integrations can continue to be maintained.

Which legacy API are you using?

Legacy REST API: The most recent legacy API. Uses HTTP Basic Auth and supports JSON/XML responses. Covers messaging, delivery reports, inbox management, keywords, credits, contacts, and groups. If you're on a legacy integration, this is most likely the one you're using.

Legacy HTTP API: The oldest EZ Texting API. Uses simple query-string parameters for authentication and returns numeric status codes. Covers basic SMS sending, credits, keywords, and voice broadcast.

Legacy incoming message APIs: Webhook-style APIs where EZ Texting forwards inbound messages (keyword submissions and inbox replies) to your server via HTTP GET requests.

Migrating to the current API

We strongly recommend migrating to the current EZ Texting API. The current API offers OAuth 2.0 authentication, improved rate limits, richer response payloads, and webhook support. See the Legacy migration guide for step-by-step instructions.


Did this page help you?