Getting started
The EZ Texting API is a REST API for sending and receiving text messages at any scale (one password-reset code or a campaign to a hundred thousand contacts), plus everything around it: contacts and groups, keywords and opt-in, templates and media, delivery reporting, and webhooks.
Everything is plain HTTPS and JSON. Any language with an HTTP client works; there's nothing to install.
Send a message in one call
curl -X POST https://a.eztexting.com/v1/messages \
-u "$EZTEXTING_USERNAME:$EZTEXTING_PASSWORD" \
-H "Content-Type: application/json" \
-d '{"toNumbers": ["15551234567"], "message": "Your table is ready!"}'import os, requests
requests.post(
"https://a.eztexting.com/v1/messages",
auth=(os.environ["EZTEXTING_USERNAME"], os.environ["EZTEXTING_PASSWORD"]),
json={"toNumbers": ["15551234567"], "message": "Your table is ready!"},
timeout=30,
)const credentials = Buffer.from(
`${process.env.EZTEXTING_USERNAME}:${process.env.EZTEXTING_PASSWORD}`
).toString("base64");
await fetch("https://a.eztexting.com/v1/messages", {
method: "POST",
headers: { Authorization: `Basic ${credentials}`, "Content-Type": "application/json" },
body: JSON.stringify({ toNumbers: ["15551234567"], message: "Your table is ready!" }),
});<?php
$ch = curl_init("https://a.eztexting.com/v1/messages");
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_USERPWD => getenv("EZTEXTING_USERNAME") . ":" . getenv("EZTEXTING_PASSWORD"),
CURLOPT_HTTPHEADER => ["Content-Type: application/json"],
CURLOPT_POSTFIELDS => json_encode(["toNumbers" => ["15551234567"], "message" => "Your table is ready!"]),
]);
curl_exec($ch);
curl_close($ch);require "net/http"
require "json"
uri = URI("https://a.eztexting.com/v1/messages")
req = Net::HTTP::Post.new(uri, "Content-Type" => "application/json")
req.basic_auth(ENV.fetch("EZTEXTING_USERNAME"), ENV.fetch("EZTEXTING_PASSWORD"))
req.body = { toNumbers: ["15551234567"], message: "Your table is ready!" }.to_json
Net::HTTP.start(uri.host, uri.port, use_ssl: true) { |http| http.request(req) }String basicAuth = Base64.getEncoder().encodeToString(
(System.getenv("EZTEXTING_USERNAME") + ":" + System.getenv("EZTEXTING_PASSWORD")).getBytes());
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://a.eztexting.com/v1/messages"))
.header("Authorization", "Basic " + basicAuth)
.header("Content-Type", "application/json")
.POST(HttpRequest.BodyPublishers.ofString(
"{\"toNumbers\": [\"15551234567\"], \"message\": \"Your table is ready!\"}"))
.build();
HttpClient.newHttpClient().send(request, HttpResponse.BodyHandlers.ofString());var credentials = Convert.ToBase64String(Encoding.UTF8.GetBytes(
$"{Environment.GetEnvironmentVariable("EZTEXTING_USERNAME")}:{Environment.GetEnvironmentVariable("EZTEXTING_PASSWORD")}"));
using var client = new HttpClient();
client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic", credentials);
await client.PostAsJsonAsync("https://a.eztexting.com/v1/messages",
new { toNumbers = new[] { "15551234567" }, message = "Your table is ready!" });body := []byte(`{"toNumbers": ["15551234567"], "message": "Your table is ready!"}`)
req, _ := http.NewRequest("POST", "https://a.eztexting.com/v1/messages", bytes.NewReader(body))
req.SetBasicAuth(os.Getenv("EZTEXTING_USERNAME"), os.Getenv("EZTEXTING_PASSWORD"))
req.Header.Set("Content-Type", "application/json")
resp, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()That's a complete, working send. The same endpoint handles MMS (mediaUrl), scheduling (sendAt), templates (messageTemplateId), and sends to whole groups (groupIds).
What you can build
Send SMS and MMS to numbers or groups, schedule for later, personalize with templates, and list or delete what you've sent.
Create and update contacts one at a time or in batches, organize them into groups, and extend them with custom fields.
Read two-way message threads per contact, track unread counts, and archive or restore threads.
Check, acquire, and configure keywords so people can opt in by texting a word to your number.
Save reusable message templates with ${FirstName}-style variables and upload media for MMS.
Delivery, engagement, and link-click reports for any message, in aggregate or per recipient.
Get inbound texts and keyword opt-ins pushed to your server the moment they happen.
Check your balance, buy credits, and block numbers from receiving further messages.
The basics
| Base URL | https://a.eztexting.com. All endpoints are under /v1/. HTTPS only. |
| Authentication | HTTP Basic (username + password) or OAuth 2.0 bearer tokens. Tokens last 90 minutes and are refreshable. → Authentication |
| Format | JSON request bodies (Content-Type: application/json) and JSON responses. |
| Phone numbers | Most common formats are accepted; store and send the canonical form (11 digits, country code first): 15551234567. → Phone number formatting |
| Rate limit | 200 requests per minute. Over the limit returns 429 with an X-Rate-Limit-Retry-After-Milliseconds header. → Rate limits |
| Pagination | List endpoints take page (0-based) and size (10, 20, 50, 100, or 200) and return content, totalElements, totalPages. → Pagination |
| Errors | Standard HTTP status codes plus a JSON body with status, title, detail, and an errors array. → Errors |
| Credits | Each SMS segment and each MMS consumes credits from your plan or anytime balance. → GET /v1/credits |
Key concepts
One endpoint, two kinds of send. POST /v1/messages sends to a list of toNumbers or to one or more groupIds. Whether a send is transactional or a campaign depends on why you send it, not how many numbers it goes to: a text triggered by something the customer did is transactional; a promotion or announcement is a campaign, even to one number. Same request shape, same response, same reports.
Opt-outs are enforced for you. When a contact replies STOP (or any standard opt-out keyword), EZ Texting marks them opted out and will not deliver further messages to them, even if your code tries. Your integration doesn't have to implement that logic, but it should read optOut and respect it in its own UI.
More in Core concepts.
Pick a path
| I want to… | Start here |
|---|---|
| Send my first message | Quickstart |
| Confirm delivery and receive replies | Send, track & receive |
| Send reminders before an appointment | Appointment reminders |
| Send a verification code | One-time passcodes |
| Notify customers about orders and shipping | Order & shipping notifications |
| Handle replies and run a support inbox | Two-way conversations |
| Send to thousands of contacts at once | Campaigns to a group |
| Get notified when someone texts me | Webhooks |
| Stay compliant (TCPA, 10DLC, opt-in) | Compliance |
| Figure out why something isn't working | Troubleshooting |
| Test safely before launch | Testing your integration |
| Avoid double-sending on retries | Idempotency & retries |
| Use the API from an AI assistant | AI assistants & the MCP server |
| Kick off an automation workflow from my app | Core concepts: Workflows |
| Copy a complete, working integration | End-to-end example: reminder service |
Resources
- API Reference — try any endpoint from the browser with your own credentials.
- Status page — current platform status and incident history.
- Support — when you need a human.
- Legacy API migration — moving from the older REST or HTTP APIs.
Updated about 16 hours ago