Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / EZ Texting API
EZ Texting API logo

EZ Texting API

70
AI ReadinessAI-Aware (B+)70/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCommunicationsSms Messagingbearer17 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Use for: I need to send an SMS to a customer, Add a new contact to an EZ Texting list, Create a group of contacts for a segmented campaign, Configure a keyword that triggers an autoresponder

Not supported: Does not handle voice calls, email delivery, or push notifications - use for SMS and MMS messaging, contact, group and keyword management only.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feztexting.com%2Feztexting" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feztexting.com%2Feztexting" | 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.

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

Patterns agents use EZ Texting 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 your Jentic One instance, 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

/keywords

Configure a new inbound keyword

POST

/media

Upload picture-message media

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

E

EZ Texting API

- AI-Aware (B+)
70/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
51
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

51

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4
40%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

65%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

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 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 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.

GET STARTED

Start building with EZ Texting API

Explore with Jentic One
View OpenAPI Document