Transactional Messaging

Send an SMS

Two fields are required: toNumbers and message. messageType is optional — EZ Texting auto-detects (SMS vs. MMS) based on whether media is attached. A 201 response means the message is queued for delivery.

cURL

Copy

curl --request POST \
     --url https://a.eztexting.com/v1/messages \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --user 'your_username:your_password' \
     --data '{
  "toNumbers": [
    "15551234567"
  ],
  "message": "Your appointment is confirmed for tomorrow at 2pm."
}'

Send an MMS

Set messageType to "MMS" (or let auto-detect handle it when you include media) and attach media via mediaUrl — a publicly accessible URL, up to 5 MB — or mediaFileId for a file uploaded through the Media Files API.

For high-volume or time-sensitive sends, pre-upload media via POST /v1/media-files and reference the returned mediaFileId. This avoids latency from fetching the URL at send time.

cURL

Copy

curl --request POST \
     --url https://a.eztexting.com/v1/messages \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --user 'your_username:your_password' \
     --data '{
  "toNumbers": [
    "15551234567"
  ],
  "message": "Check out our new menu!",
  "mediaUrl": "https://example.com/menu.jpg"
}'

Schedule a message

Include sendAt with an ISO 8601 timestamp to schedule future delivery. Omit it to send immediately. Save the returned message ID so you can cancel with DELETE /v1/messages if plans change.

cURL

Copy

curl --request POST \
     --url https://a.eztexting.com/v1/messages \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --user 'your_username:your_password' \
     --data '{
  "toNumbers": [
    "15551234567"
  ],
  "message": "Your appointment is in 1 hour.",
  "sendAt": "2026-01-15T14:00:00Z"
}'

Check delivery status

Retrieve a message's delivery status with GET /v1/message-details/{id}. For production systems, use webhooksinstead of polling — you'll get real-time delivery notifications pushed to your server.

cURL

Copy

curl --request GET \
     --url https://a.eztexting.com/v1/message-details/123456789 \
     --header 'accept: application/json' \
     --user 'your_username:your_password'

All message parameters

Message types

SMS— Standard text. Up to 160 characters (GSM-7) sends as one segment; longer messages split into multiple segments and reassemble on the recipient's device. Emoji/Unicode use UCS-2 (70 chars per segment).

MMS — Rich media messages with images, video, or audio alongside text. Attach via mediaUrl or mediaFileId.

Message templates

Templates let you define reusable message content and reference it by ID when sending. Create with POST /v1/message-templates (requires name and message), then pass messageTemplateId when sending. Keeps your sending code clean and lets non-technical teams manage content separately. See the Message Templates API reference.

Delivery reports

For detailed per-recipient reporting, use the Message Reports endpoints:

• GET /v1/message-reports/{id} — Overall delivery summary
• GET /v1/message-reports/{id}/responses/delivery — Per-recipient delivery statuses
• GET /v1/message-reports/{id}/responses/engagement — Engagement metrics
• GET /v1/message-reports/{id}/responses/link — Link click tracking

Error handling

Next steps

• Marketing Campaigns — Send to multiple recipients or contact groups
• Conversational Messaging — Manage two-way threads when contacts reply
• Contact Management — Build and organize your audience
• Automations — Trigger messages with keywords and webhooks
• API Reference — Full interactive endpoint documentation