EZ Texting provides a REST API for developers to integrate with their platform. Here are the key points about EZ Texting's API:
In summary, EZ Texting provides a modern REST API for developers to integrate SMS messaging capabilities into their applications, with a focus on flexibility and ease of use.
EZ Texting offers both REST and HTTP APIs, with the REST API being the recommended and actively developed option. The API documentation covers functionality like sending SMS/MMS messages, managing contacts and groups, retrieving message status, and handling incoming messages through the Keyword API and Inbox Reply API. The API uses OAuth authentication.
However, the search results do not contain any information about webhooks or event subscriptions in the official EZ Texting API documentation. To get a definitive answer, it is recommended to:
If webhooks are indeed not available, you may need to implement polling mechanisms to check for updates or changes in your EZ Texting account programmatically.
Based on the search results provided, here are the key points regarding API rate limits for the EZ Texting API:
EZ Texting imposes a limit on the number of simultaneous connections that can be made from a server to theirs per second.
To avoid having your IP blocked, you should not attempt to make more than 2 simultaneous HTTP connections per second to their servers.
If your application exceeds this limit, you may receive a rate limiting error with the HTTP status code 503 in the header, and your request will not be processed.
When sending multiple requests, EZ Texting strongly suggests using the following logic to avoid rate limiting:
For sending the same message to multiple recipients, EZ Texting strongly urges users to consider using their REST API instead of the HTTP API.
The REST API allows passing a single message and an array of phone numbers to deliver in a single request, which is more efficient than making multiple individual requests.
EZ Texting encourages users to use their REST API over the HTTP API, as the HTTP API is considered a legacy product.
The REST API offers new bulk sending and message scheduling options that are not available in the HTTP API.
No new features will be added to the HTTP API.
It's important to note that while these rate limits are mentioned for the HTTP API, the search results do not provide specific information about rate limits for the REST API. For the most up-to-date and accurate information on API rate limits, especially for the REST API, it would be best to consult the official EZ Texting API documentation or contact their support team directly.
Based on the search results provided, I could not find a specific mention of the most recent version of the EZ Texting API. However, I can provide some relevant information about EZ Texting's API offerings:
EZ Texting offers both REST and HTTP APIs [1].
The REST API is the more current and actively developed version [1].
The HTTP API is considered a legacy product, with no new features being added [1].
EZ Texting encourages users to use the REST API over the HTTP API [1][3].
The REST API offers newer features such as bulk sending and message scheduling options [3].
While the search results don't mention a specific version number, they do indicate that EZ Texting is in the process of transitioning from their legacy API to a new API:
The documentation for both REST and HTTP APIs is labeled as referring to their "Legacy API" [1][2].
There are mentions of a new API that will replace the legacy version [1][2][3].
The legacy API is unavailable for new users and will be deprecated for existing users soon [1][2].
Based on this information, if you're looking to integrate with EZ Texting's API, it's recommended to:
Use the REST API rather than the HTTP API, as it's the more current version.
Check EZ Texting's developer documentation for the most up-to-date information on their new API, which is set to replace the legacy versions.
Contact EZ Texting directly for the most current information on their API versions and availability, as they appear to be in a transition period.
It's important to note that without more recent or specific information, it's not possible to provide the exact version number of the most recent EZ Texting API. For the most accurate and up-to-date information, it would be best to consult EZ Texting's official documentation or contact their support directly.
To get a developer account for EZ Texting to create an API integration, you'll need to follow these steps:
Create an EZ Texting account:
Familiarize yourself with the API documentation:
Obtain API credentials:
Set up your development environment:
Test the API:
Implement your integration:
Here are the key data models you can interact with using the EZ Texting API:
The API allows you to programmatically manage most aspects of your EZ Texting account, from contact and group management to sending various types of messages and configuring keywords. The REST API is recommended for new integrations as it offers more advanced features like bulk sending compared to the legacy HTTP API.
