SMS API for Developers

Disabling TLS 1.0 & SSL encryption protocols on June 30th 2018 - What You Need to Know

As part of continuous improvements to our systems, we are disabling support for TLS 1.0 & SSL encryption. Only TLS 1.2 and above will be supported going forward. This is in accordance with Industry practice for improved security. Outgoing https connections from our servers to any customer server will be supported over TLS 1.1/1.2. After this change, you cannot connect to our APIs over TLS 1.0. Get the full story and next steps here.

***

Leverage the power of EZ Texting's flexible Bulk SMS API to allow your application to send text messages through our SMS gateway. Whether you're an independent developer or you work on a team at a Fortune 500 company, we're here to provide you with the right tools and the support you deserve. Our SMS gateway is robust, reliable, and easy to use.

We offer a REST API and a legacy HTTP API. While we will continue to support our HTTP API, this is a legacy product. Active development has moved to our REST API. As such, we encourage you to use our REST API. The REST API already offers new bulk sending and message scheduling options. No new features will be added to the HTTP API. Regardless of the API you choose, incoming messages are handled by our Incoming Message API.

Lastly, feel free to explore our C# SDK. You can download it from the NuGet package manager or directly from GitHub.

Read The Documentation

Before you begin working with our text messaging API you'll want to read through the documentation. We Offer REST & HTTP APIs. Please make sure to read the documentation for the API that you are using.

If you are sending the same message to multiple recipients our REST API allows you to pass us an array of phone numbers. The HTTP API requires you to loop through each phone number. The HTTP API is a legacy product.

Read The REST API Docs

Read The Incoming Message API Docs

Read The HTTP API Docs (LEGACY)

EZ Texting API REST Client

A Java client guide is available for the REST API. This includes requirements, code examples, endpoints documentation, and answers to frequently asked questions. Click here for a link to the repository.

See Code Examples

REST API Code Examples
Browse through our code examples to see basic implementations of the various API functions.

• PHP
• C#
• Java
• Perl
• Python
• Ruby
   

HTTP API Code Examples
Browse through our code examples to see basic implementations of the HTTP API.

Developing for EZ Texting in Ruby? Check out our SMS gem.

Our gem uses the legacy HTTP API.

Get Started With Our REST SMS API

We've put together a step-by-step guide to help you learn the ins and outs of the REST API. Ready to go? Jump right in.

Not looking to implement the API yourself? No problem, check out our recommended partners page to see a list of developers and firms who have successfully implemented the EZ Texting API for their clients.

Explore Our C# SDK

Check out our C# SDK using the resources below.

C# Project Page
Getting Started Guide
Code Samples

The Buzz About Our APIs

"Up front pricing, easy to set up, well documented and easy to use API."
    - CCR Technology Group

The service offers easy API integration and a wide carrier support for the US.
    - Hovland Conservatory of Music 

I love the API! It's super easy to use and has integrated flawlessly with my system. I love the price, it keeps me competitive.
    - MinistryPal

An easy to use API with .NET integration; competitive pricing.
    - Five Talent Software

Customer Spotlight

Hundreds of customers use our API to power text messaging in their application every day. We're constantly amazed to see what you can do with our API. Visit the Customer Spotlight section to read about new and interesting implementations of our API.

Connect With A Recommended Partner

Does this all sound a bit too difficult for you? That's not a problem at all - visit the recommended partners section to get in touch with talented developers who have experience connecting web applications to the EZ Texting platform.