canonical: https://jentic.com/apis/eztexting.com/eztexting # EZ Texting API 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. ## For AI 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. ## Scope Does not handle voice calls, email delivery, or push notifications - use for SMS and MMS messaging, contact, group and keyword management only. ## Capabilities - 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} - Upload picture-message media using /media for MMS campaigns ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance, so the agent can send transactional SMS, update contacts, and configure keywords without ever holding the raw access token. Example prompt: 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 | 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 | ## Key resources - **Messages** — Send messages and retrieve delivery details - **Contacts** — Create, read and update SMS subscribers - **Groups** — Segment contacts into targetable groups - **Keywords** — Configure inbound keywords and autoresponders - **Media** — Upload picture-message media for MMS sends ## Why Jentic - **Setup:** Wiring the EZ Texting API by hand means minting its bearer token, targeting the api.eztexting.com/v2 host, and coordinating messages, contacts, groups, and media yourself. Through Jentic you install once, import the EZ Texting API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** EZ Texting carries the message and contact details in the request body, so you limit the agent to the operations it needs, such as sending a message or adding a contact. You choose those operations, so group or keyword management is not included unless you add it. - **Credential handling:** Your EZ Texting bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. The long-lived access token never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a transactional SMS' or 'add a contact to a group', and Jentic returns the matching /messages or /contacts operation with its full input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ezeep Blue Printing API** — Cloud printing - pair with EZ Texting when an SMS confirmation should accompany a printed receipt or label. - **Exude API Service** — Lightweight English text preprocessing - useful when SMS reply transcripts need stop-word stripping before analysis. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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. ### Can I limit what my agent is allowed to do with the EZ Texting API? Yes. Because Jentic One is self-hosted, you decide which EZ Texting operations your agent can call and which credentials it may use. You can allow only what the workflow needs, such as sending a message with POST /messages or adding a subscriber with POST /contacts, while leaving group and keyword management out unless you choose to include them. The bearer token stays in your own instance and is supplied at execution time, so the agent never holds the raw credential.