TextUs Next API

Name: TextUs Next API
Brand: TextUs Next API
Availability: InStock

✓ Official Vendor SpecCommunicationsSms Messagingbearer37 EndpointsREST

For Agents

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

I need to contact, I want to contacts, Search for contact, Find all contact

Install Jentic One Beta

Connect the TextUs Next API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TextUs Next 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%2Ftextus.com%2Ftextus" | sh

Step 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%2Ftextus.com%2Ftextus" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with TextUs Next API.

Create contact

List contacts

Get contact

Update contact

GET STARTED

Start building with TextUs Next API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use TextUs Next API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

37 endpoints — api for the textus business texting platform.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using TextUs Next API through Jentic.

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.

TextUs Next API

Connect the TextUs Next API to your agent

Capabilities

Start building with TextUs Next API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs