Text Request API v3
56
AI ReadinessFoundational (C)56/100
Community OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey61 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically post an mms attachment to text request., sends a message. Covers 61 operations with apiKey authentication.
Use for: I need to post an mms attachment to text request., I want to sends a message, Search for a new dashboard with the given name and phone number, Find all all dashboards in an account.
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
This page contains documentation for Text Request's v3 API. [Click here](https://www.textrequest.com/api/v2) for v2 documentation. The Text Request API makes it easy to programmatically interact with your Text Request account. It provides the ability to **send messages**, **retrieve conversations**, **send payment requests**, **manage contacts, groups, dashboards, and users**, and **create and del. The API exposes 61 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Text Request API v3 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Text Request API v3, 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%2Ftextrequest.com%2Ftextrequest" | sh2
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%2Ftextrequest.com%2Ftextrequest" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Text Request API v3 API.
Post an MMS attachment to Text Request.
Sends a message
Create a new dashboard with the given name and phone number
Get all dashboards in an account.
Update a specific dashboard's name
Deletes the specified dashboard.
Use Cases
Patterns agents use Text Request API v3 API for, with concrete tasks.
★ Communications Operations
Use the Text Request API v3 to perform communications operations programmatically. The API provides 61 endpoints covering core functionality including post an mms attachment to text request., sends a message, create a new dashboard with the given name and phone number.
Call POST /mms to post an mms attachment to text request.
Automated Messages Management
Automate messages operations by combining multiple Text Request API v3 endpoints. Agents can sends a message and then create a new dashboard with the given name and phone number in a single workflow.
Call POST /messages to sends a message, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Text Request API v3 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'post an mms attachment to text request.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
61 endpoints — this page contains documentation for text request's v3 api.
METHOD
PATH
DESCRIPTION
POST
/mms
Post an MMS attachment to Text Request.
POST
/messages
Sends a message
POST
/dashboards
Create a new dashboard with the given name and phone number
GET
/dashboards
Get all dashboards in an account.
GET
/dashboards/{dashboard_id}
Get info on this specific dashboard
PUT
/dashboards/{dashboard_id}
Update a specific dashboard's name
DELETE
/dashboards/{dashboard_id}
Deletes the specified dashboard.
GET
/dashboards/provisioning
Get available provisioned numbers for hosting with a dashboard
POST
/mms
Post an MMS attachment to Text Request.
POST
/messages
Sends a message
POST
/dashboards
Create a new dashboard with the given name and phone number
GET
/dashboards
Get all dashboards in an account.
GET
/dashboards/{dashboard_id}
Get info on this specific dashboard
PUT
/dashboards/{dashboard_id}
Update a specific dashboard's name
DELETE
/dashboards/{dashboard_id}
Deletes the specified dashboard.
GET
/dashboards/provisioning
Get available provisioned numbers for hosting with a dashboard
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.
T
Text Request API v3
- Foundational (C)56/100
67
Foundational Compliance69
Developer Experience & Jentic Compatibility33
AI-Readiness & Agent Experience92
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
67
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
37%
Example Density
How richly the API is illustrated with examples.
88%
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.
33
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
60%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
70%
Summary Coverage
Coverage of summaries across operations/tags/info.
92
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
92%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Text Request by hand means setting its x-api-key header on every request to api.textrequest.com and handling the messaging and dashboard endpoints yourself. Through Jentic you install once, import Text Request from the API Directory, store the key once, and your agent calls it.
Permission scoping
Text Request puts the dashboard id in the URL path (/dashboards/{dashboard_id}), so a rule can pin your agent to one dashboard for reads. You choose the operations it may call, so destructive ones like deleting a dashboard are not included unless you add them.
Credential isolation
Your Text Request API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send an MMS attachment' or 'list dashboards', and Jentic returns the matching Text Request operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Text Request API v3 API through Jentic.
What authentication does the Text Request API v3 use?
The Text Request API v3 uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I post an mms attachment to text request. with the Text Request API v3?
Yes. Use the POST /mms endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Text Request API v3?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I post an mms attachment to text request. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post an mms attachment to text request.'. Jentic returns the matching Text Request API v3 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Text Request API v3 have?
The Text Request API v3 exposes 61 endpoints covering messages, payments, contacts operations.
Can I limit what my agent is allowed to do with the Text Request API?
Yes. Because you run Jentic One yourself, your own rules decide which Text Request operations and credentials the agent may use. Since the dashboard id sits in the URL path at /dashboards/{dashboard_id}, you can pin the agent to a single dashboard and grant only read operations like GET /dashboards. Destructive calls such as DELETE /dashboards/{dashboard_id} stay off unless you explicitly add them, so an agent that only sends messages via POST /messages never gains the ability to delete a dashboard.
GET STARTED