EZ Texting API

Name: EZ Texting API API
Brand: EZ Texting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbearer17 EndpointsREST

For Agents

Send SMS messages, manage contacts, groups and keywords, and upload media for the EZ Texting v2 platform across 17 endpoints under api.eztexting.com/v2.

Connect the EZ Texting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EZ Texting API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with EZ Texting API API.

Send and retrieve SMS messages through /messages and /messages/{id}

Manage opt-in contacts with /contacts and /contacts/{id} for create, read and update flows

Group contacts for segmented sends through /groups and /groups/{id}

Configure inbound keywords for autoresponders via /keywords and /keywords/{id}

GET STARTED

Start building with EZ Texting API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for EZ Texting API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for EZ Texting API, keeping it validated and agent-ready. EZ Texting is an SMS marketing and messaging platform, and the v2 API exposes the operations needed to send messages, manage contacts and groups, configure keywords for inbound responses, and upload media for picture messaging. Authentication is HTTP Bearer, and the surface is sized for marketers and operations teams running mass SMS programmes.

Use Cases

Patterns agents use EZ Texting API API for, with concrete tasks.

★ Transactional SMS Sends

Use POST /messages to send transactional SMS notifications such as appointment reminders or order updates from a backend service. Pair with /messages/{id} to fetch the delivery state of any individual message and feed status changes back into the originating system. EZ Texting handles carrier routing and sender IDs while the API surface stays small.

POST /messages with the recipient phone number and reminder copy, then poll GET /messages/{id} to verify the delivery status.

Campaign Audience Management

Build segmented SMS campaigns by maintaining contacts and groups through the /contacts and /groups endpoints. Add subscribers when they opt in, attach them to one or more groups for targeting, and update their attributes when their preferences change. The 17-endpoint surface keeps audience operations explicit and easy to script.

POST /contacts to enrol a new subscriber, then POST /groups/{id} membership to add them to the launch-day campaign group.

Inbound Keyword Autoresponders

Configure inbound SMS keywords through /keywords so that subscribers texting a phrase like JOIN to the short code receive an automated reply and are added to the opt-in list. Keywords drive growth-loop mechanics for SMS marketing programmes and can be combined with group membership for follow-up nurture sends.

POST /keywords with the keyword JOIN and the autoresponder copy, then verify the configuration with GET /keywords/{id}.

MMS with Picture Messaging

Upload an image via /media and reference it from a /messages send to deliver picture messages as part of an MMS campaign. Useful for promotions and event invitations where a visual asset increases engagement, and for transactional sends like badge images or coupon codes that benefit from rich media.

POST /media with the campaign image, then POST /messages referencing the returned media id and the recipient list.

Agent-Driven SMS Workflows via Jentic

An AI agent that manages customer communications can use Jentic to discover and call EZ Texting operations rather than embedding the v2 client. Bearer tokens stay inside the Jentic vault, so the agent can send transactional SMS, update contacts, and configure keywords without ever holding the raw access token.

Through Jentic, search 'send a transactional SMS', load POST /messages, and execute it with the recipient and message body for the agent's reminder workflow.

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for ez texting api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/messages

Send a new SMS or MMS message

GET

/messages/{id}

Retrieve a sent message and its status

POST

/contacts

Create a new SMS subscriber

GET

/contacts/{id}

Retrieve a contact

POST

/groups

Create a new contact group

POST

/keywords

Configure a new inbound keyword

POST

/media

Upload picture-message media

POST

/messages

Send a new SMS or MMS message

GET

/messages/{id}

Retrieve a sent message and its status

POST

/contacts

Create a new SMS subscriber

GET

/contacts/{id}

Retrieve a contact

POST

/groups

Create a new contact group

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

EZ Texting bearer tokens are stored encrypted in the Jentic vault; agents receive a scoped token at execution time and never handle the long-lived access token.

Intent-based discovery

Agents search Jentic for intents like 'send a transactional SMS' or 'add a contact to an EZ Texting group' and Jentic returns the matching /messages or /contacts operation with its full input schema.

Time to first call

Direct integration: 1-2 days to wire bearer auth, contact and group flows, and delivery-status polling. Through Jentic: under an hour to search, load, and execute the first send.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

ezeep Blue Printing API

Cloud printing — pair with EZ Texting when an SMS confirmation should accompany a printed receipt or label.

Use ezeep Blue to print the receipt after the EZ Texting SMS confirmation has been delivered to the customer.

Complementary

Exude API Service

Lightweight English text preprocessing — useful when SMS reply transcripts need stop-word stripping before analysis.

Run inbound SMS replies through Exude before indexing them for search or sentiment analysis.

FAQs

Specific to using EZ Texting API API through Jentic.

Why is there no official OpenAPI spec for EZ Texting API?

EZ Texting does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EZ Texting API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the EZ Texting API use?

The spec declares an HTTP Bearer scheme called bearerAuth. Provision the token from your EZ Texting account and store it in the Jentic vault so it is supplied as the Authorization header without entering the agent prompt.

Can I send an MMS through the EZ Texting API?

Yes. Upload the image with POST /media, then call POST /messages referencing the returned media id alongside the recipient phone number to deliver a picture-message MMS.

How do I configure a keyword autoresponder?

Call POST /keywords with the inbound keyword and autoresponder copy, then verify with GET /keywords/{id}; subscribers texting that keyword to your assigned number receive the configured reply.

How do I send a transactional SMS through Jentic?

Run pip install jentic, search 'send a transactional SMS', load POST /messages, then execute it with the recipient phone number and message body; Jentic injects the bearer token from the vault.

What are the rate limits for the EZ Texting API?

The spec does not declare explicit rate limits, so respect any 429 responses with backoff and stagger high-volume sends; the EZ Texting account dashboard is the source of truth for the per-tier throughput allowance.