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

# Textellent API

Textellent engages and keeps customers through text messaging for marketing, sales, and customer service. Provides APIs for sending messages, managing contacts, tags, appointments, and webhook subscriptions. The API exposes 24 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send message, create contacts. Covers 24 operations with apiKey authentication.

## Scope

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

## Capabilities

- Send Message
- Create Contacts
- List Contacts
- Update Contact
- Get Contact
- Delete Contact
- Find Contact

## Use cases

### Payments Operations

Use the Textellent API to perform payments operations programmatically. The API provides 24 endpoints covering core functionality including send message, create contacts, list contacts.

Example prompt: Call POST /messages.json to send message

### Automated Cancelappointment.Json Management

Automate cancelappointment.json operations by combining multiple Textellent API endpoints. Agents can create contacts and then list contacts in a single workflow.

Example prompt: Call POST /contacts.json to create contacts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Textellent 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.json` | Send Message |
| POST | `/contacts.json` | Create Contacts |
| GET | `/contacts.json` | List Contacts |
| PUT | `/contacts.json` | Update Contact |
| GET | `/contacts/{contactId}.json` | Get Contact |
| DELETE | `/contacts/{contactId}.json` | Delete Contact |
| GET | `/findContact.json` | Find Contact |
| GET | `/findContactWithMultiplePhoneNumbers.json` | Find Contact by Multiple Phone Numbers |

## Key resources

- **Cancelappointment.Json** — Operations for cancelAppointment.json
- **Contacts** — Operations for contacts
- **Contacts.Json** — Operations for contacts.json
- **Createappointment.Json** — Operations for createAppointment.json
- **Event** — Operations for event

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 68 / 100
- **View full report:** https://jentic.com/apis/textellent.com/textellent/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 Textellent by hand means setting its two API-key headers, the authCode and the partnerClientCode, on every request to client.textellent.com and handling errors yourself. Through Jentic you install once, import Textellent from the API Directory, store the keys once, and your agent calls it.
- **Permission scoping:** Textellent puts the contact id in the URL path (`/contacts/{contactId}.json`), so a rule can pin your agent to one contact for reads. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.
- **Credential handling:** Your Textellent API keys are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a text message' or 'find a contact by phone number', and Jentic returns the matching Textellent operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Textellent API use?

The Textellent API uses an API key passed in the `authCode` 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 Textellent API?

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

### What are the rate limits for the Textellent 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 Textellent API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Textellent API exposes 24 endpoints covering cancelappointment.json, contacts, contacts.json operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which of the 24 Textellent operations your agent may call and which stored API keys it may use. Because Textellent puts the contact id in the URL path (`/contacts/{contactId}.json`), you can pin the agent to a single contact for read operations like GET `/contacts/{contactId}.json.` Destructive operations such as DELETE `/contacts/{contactId}.json` or sending messages via POST /messages.json are excluded unless you explicitly grant them.