For Agents
Programmatically send message, create contacts. Covers 24 operations with apiKey authentication.
Use for: I need to send message, I want to contacts, Search for contacts, Find all contact
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
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.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Textellent API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftextellent.com%2Ftextellent" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftextellent.com%2Ftextellent" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Textellent API.
Send Message
Create Contacts
List Contacts
Update Contact
Get Contact
Delete Contact
Find Contact
Patterns agents use Textellent API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'send message', load the operation schema, and execute with Jentic-managed credentials
24 endpoints — textellent engages and keeps customers through text messaging for marketing, sales, and customer service.
METHOD
PATH
DESCRIPTION
/messages.json
Send Message
/contacts.json
Create Contacts
/contacts.json
List Contacts
/contacts.json
Update Contact
/contacts/{contactId}.json
Get Contact
/contacts/{contactId}.json
Delete Contact
/findContact.json
Find Contact
/findContactWithMultiplePhoneNumbers.json
Find Contact by Multiple Phone Numbers
/messages.json
Send Message
/contacts.json
Create Contacts
/contacts.json
List Contacts
/contacts.json
Update Contact
/contacts/{contactId}.json
Get Contact
/contacts/{contactId}.json
Delete Contact
/findContact.json
Find Contact
/findContactWithMultiplePhoneNumbers.json
Find Contact by Multiple Phone Numbers
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Specific to using Textellent API through Jentic.
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.
GET STARTED