canonical: https://jentic.com/apis/textit.in/textit

# Textit In TextIt API

TextIt is a visual flow builder for SMS, voice, and messaging apps. The v2 API provides a RESTful JSON interface for managing contacts, broadcasts, campaigns, flows, messages, and more. The API exposes 17 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list archives of messages and runs, send a broadcast message. Covers 17 operations with apiKey authentication.

## Scope

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

## Capabilities

- List archives of messages and runs
- Send a broadcast message
- Create or update a contact
- Delete a contact
- Perform bulk contact actions (add/remove groups, etc.)

## Use cases

### Communications Operations

Use the TextIt API to perform communications operations programmatically. The API provides 17 endpoints covering core functionality including list archives of messages and runs, send a broadcast message, list broadcasts.

Example prompt: Call GET /archives.json to list archives of messages and runs

### Automated Archives Management

Automate archives operations by combining multiple TextIt API endpoints. Agents can send a broadcast message and then list broadcasts in a single workflow.

Example prompt: Call POST /broadcasts.json to send a broadcast message, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TextIt 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 'list archives of messages and runs', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/archives.json` | List archives of messages and runs |
| POST | `/broadcasts.json` | Send a broadcast message |
| GET | `/broadcasts.json` | List broadcasts |
| POST | `/contacts.json` | Create or update a contact |
| GET | `/contacts.json` | List contacts |
| DELETE | `/contacts.json` | Delete a contact |
| POST | `/contact_actions.json` | Perform bulk contact actions (add/remove groups, etc.) |
| GET | `/flows.json` | List flows |

## Key resources

- **Archives** — Operations related to Archives
- **Broadcasts** — Operations related to Broadcasts
- **Contacts** — Operations related to Contacts
- **Fields** — Operations related to Fields
- **Flows** — Operations related to Flows

## Why Jentic

- **Setup:** Wiring TextIt by hand means setting up its API-token auth against textit.in and handling the messaging and flow endpoints yourself. Through Jentic you install once, import TextIt from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** TextIt keeps message, contact, and flow targets in the request body on endpoints like /broadcasts.json and /contacts.json, so limit the agent to the operations it needs, such as listing archives or sending a broadcast. You choose that set, so destructive operations like deleting a contact are not included unless you add them.
- **Credential handling:** Your TextIt API token 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 a broadcast' or 'list message archives', and Jentic returns the matching TextIt 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 TextIt API use?

The TextIt API uses an API key passed in the `Authorization` 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 list archives of messages and runs with the TextIt API?

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

### What are the rate limits for the TextIt 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 list archives of messages and runs through Jentic?

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

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

The TextIt API exposes 17 endpoints covering archives, broadcasts, contacts operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which TextIt operations and credentials your agent may use, so you can grant only the endpoints it needs, such as listing archives with GET /archives.json or sending a broadcast with POST /broadcasts.json. TextIt keeps message, contact, and flow targets in the request body on endpoints like /broadcasts.json and /contacts.json, so scoping happens at the operation level: you choose the set the agent can call. Destructive operations such as deleting a contact with DELETE /contacts.json stay out of reach unless you explicitly add them.