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

# TextUs Next API

API for the TextUs business texting platform. Manage contacts, conversations, messages, campaigns, groups, and more. The API exposes 37 endpoints secured with bearer authentication.

## For AI agents

Programmatically create contact, list contacts. Covers 37 operations with bearer authentication.

## Scope

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

## Capabilities

- Create contact
- List contacts
- Get contact
- Update contact
- Delete contact

## Use cases

### Communications Operations

Use the TextUs Next API to perform communications operations programmatically. The API provides 37 endpoints covering core functionality including create contact, list contacts, get contact.

Example prompt: Call POST /{account}/contacts to create contact

### Automated Accounts Management

Automate accounts operations by combining multiple TextUs Next API endpoints. Agents can list contacts and then get contact in a single workflow.

Example prompt: Call GET /{account}/contacts to list contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TextUs Next 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 bearer tokens manually.

Example prompt: Search Jentic for 'create contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/{account}/contacts` | Create contact |
| GET | `/{account}/contacts` | List contacts |
| GET | `/{account}/contacts/{contact}` | Get contact |
| PUT | `/{account}/contacts/{contact}` | Update contact |
| DELETE | `/{account}/contacts/{contact}` | Delete contact |
| GET | `/{account}/contacts/{contact}/conversations` | Get contact conversations |
| GET | `/{account}/contacts/{contact}/tags` | Get contact tags |
| POST | `/{account}/contacts/upload` | Upload contacts |

## Key resources

- **Accounts** — Operations for accounts
- **Campaigns** — Operations for campaigns
- **Contacts** — Operations for contacts
- **Conversations** — Operations for conversations
- **Groups** — Operations for groups

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/textus.com/textus/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 TextUs Next by hand means learning its bearer auth against next.textus.com and threading the account segment through every contact request yourself. Through Jentic you install once, import TextUs from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** TextUs Next puts the account and contact ids in the URL path (/{account}/contacts/{contact}), so a rule can pin your agent to one account and its contacts. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.
- **Credential handling:** Your TextUs Next 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 'create a contact' or 'list a contact's conversations', and Jentic returns the matching TextUs Next 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 TextUs Next API use?

The TextUs Next API uses a Bearer token 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 create contact with the TextUs Next API?

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

### What are the rate limits for the TextUs Next 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 create contact through Jentic?

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

### How many endpoints does the TextUs Next API have?

The TextUs Next API exposes 37 endpoints covering accounts, campaigns, contacts operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which TextUs Next operations and credentials your agent can use. Because the API carries the account and contact ids in the URL path, such as /{account}/contacts/{contact}, you can pin the agent to a single account and its contacts. You also choose the exact operations it may call, so destructive ones like deleting a contact stay off limits unless you add them.