canonical: https://jentic.com/apis/textrequest.com/textrequest

# Text Request API v3

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.

## For AI agents

Programmatically post an mms attachment to text request., sends a message. Covers 61 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'post an mms attachment to text request.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Messages** — Sending and receiving messages
- **Payments** — Operations related to Payments
- **Contacts** — Managing contacts
- **Dashboard** — Get information on dashboards
- **Conversations** — Operations related to Conversations

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

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