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

# Textmagic API

Textmagic SMS messaging API. Send messages, manage contacts, templates, and phone numbers. The API exposes 36 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send message, list messages. Covers 36 operations with apiKey authentication.

## Scope

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

## Capabilities

- Send message
- List messages
- Get message
- Delete message
- Monitor Textmagic API operational status and events

## Use cases

### Communications Operations

Use the Textmagic API to perform communications operations programmatically. The API provides 36 endpoints covering core functionality including send message, list messages, get message.

Example prompt: Call POST /messages to send message

### Automated Contacts Management

Automate contacts operations by combining multiple Textmagic API endpoints. Agents can list messages and then get message in a single workflow.

Example prompt: Call GET /messages to list messages, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Textmagic API 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 'send message', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/messages` | Send message |
| GET | `/messages` | List messages |
| GET | `/messages/{id}` | Get message |
| DELETE | `/messages/{id}` | Delete message |
| GET | `/messages/price` | Get message price |
| GET | `/replies` | List replies |
| GET | `/sessions` | List sessions |
| GET | `/sessions/{id}` | Get session |

## Key resources

- **Contacts** — Operations related to Contacts
- **Lists** — Operations related to Lists
- **Messages** — Operations related to Messages
- **Numbers** — Operations related to Numbers
- **Schedules** — Operations related to Schedules

## AI readiness

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.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 79 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/textmagic.com/textmagic/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

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

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Textmagic by hand means setting its X-TM-Key header on every request to rest.textmagic.com and handling the messaging endpoints yourself. Through Jentic you install once, import Textmagic from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Textmagic puts the message id in the URL path (`/messages/{id}`), so a rule can pin your agent to reading one message. You choose the operations it may call, so destructive ones like deleting a message are not included unless you add them.
- **Credential handling:** Your Textmagic 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 SMS message' or 'check the price of a message', and Jentic returns the matching Textmagic 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 Textmagic API use?

The Textmagic API uses an API key passed in the `X-TM-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 send message with the Textmagic API?

Yes. Use the POST /messages endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Textmagic API?

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 send message through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send message'. Jentic returns the matching Textmagic API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Textmagic API have?

The Textmagic API exposes 36 endpoints covering contacts, lists, messages operations.

### Can I limit what my agent is allowed to do with the Textmagic API?

Yes. Because you run Jentic One yourself, your own rules decide which Textmagic operations and credentials the agent may use. You can allow it to send a message with POST /messages or read a single message with GET `/messages/{id}` while leaving destructive calls like DELETE `/messages/{id}` out entirely. Since the message id sits in the URL path, a rule can pin the agent to reading one specific message rather than the whole account.