Docs Terrareach TerraReach API

Name: TerraReach API
Brand: TerraReach API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingnone56 EndpointsREST

For Agents

Send single and bulk SMS through TerraReach, manage messaging teams, users and API keys, and integrate billing for a messaging workload.

Install Jentic One Beta

Connect the TerraReach API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TerraReach 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 TerraReach API.

Send a single SMS via the v1 or v2 SMS endpoint

Send bulk SMS to many recipients in one call

Manage TerraReach teams that group users and packages

Maintain user accounts including signup, OTP verification and password reset

GET STARTED

Start building with TerraReach API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use TerraReach API for, with concrete tasks.

★ Transactional SMS

Send shipping, appointment and verification messages via the v2 SMS endpoint. POST /v2/sms takes a recipient and message body and queues delivery. For higher volume, /v2/sms/bulk accepts arrays in one call. Lets product teams add SMS to their workflows without standing up their own SS7 gateway.

POST /v2/sms with to='+15551234567' and message='Your order ships tomorrow' to send a single transactional SMS.

Bulk Marketing or Notification Sends

For event reminders, opt-in marketing or large status updates, /v2/sms/bulk accepts a list of recipient-message pairs in a single request. This avoids per-message HTTP overhead and lets the platform optimise delivery scheduling. The earlier /v1/sms/bulk endpoint remains for clients on the legacy contract.

POST /v2/sms/bulk with a list of objects each containing to and message for an event-reminder broadcast.

Account and Team Self-Service

Build a self-service onboarding flow that creates a TerraReach user, verifies their phone with OTP, attaches them to a team, issues an API key and lets them top up balance via Stripe. The /users/verify-otp, /users/reset-password, /api-keys and /payments/stripe endpoints together cover the lifecycle without hitting a support team.

POST /users to create the account, POST /users/verify-otp to verify the phone, POST /api-keys to issue a key, then POST /payments/stripe to add balance.

AI Agent Customer Notification Service

Through Jentic, an AI agent embedded in a customer-service workflow can send personalised SMS confirmations and updates. The agent searches Jentic for the SMS intent, loads the v2 SMS operation and executes against the configured TerraReach environment. This avoids a custom integration and keeps message templating in the agent rather than in TerraReach.

Use Jentic to search 'send TerraReach SMS', load /v2/sms, and execute it with the customer's number and the templated message.

Key Endpoints

56 endpoints — jentic publishes the only available openapi specification for terrareach api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/sms

Send a single SMS message

POST

/v2/sms/bulk

Send SMS to many recipients in one call

POST

/v1/sms

Send a single SMS using the v1 contract

POST

/v1/sms/bulk

Bulk SMS using the v1 contract

POST

/users/verify-otp

Verify a user's phone with an OTP

POST

/users/reset-password

Reset a user's password

POST

/api-keys

Create a new API key

POST

/payments/stripe

Top up balance via Stripe

POST

/v2/sms

Send a single SMS message

POST

/v2/sms/bulk

Send SMS to many recipients in one call

POST

/v1/sms

Send a single SMS using the v1 contract

POST

/v1/sms/bulk

Bulk SMS using the v1 contract

POST

/users/verify-otp

Verify a user's phone with an OTP

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

TerraReach API keys are stored encrypted in the Jentic vault. Agents receive scoped access via Jentic's MAXsystem and never see the raw key, which matters because messaging keys are a common abuse target if leaked.

Intent-based discovery

Agents search by intent (for example 'send an SMS' or 'verify a user phone') and Jentic returns the matching TerraReach operations such as /v2/sms or /users/verify-otp with their input schemas, so the agent calls the right endpoint without parsing 56 routes of docs.

Time to first call

Direct TerraReach integration: 1-2 days for auth wiring, message-shape parsing and payment-flow handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using TerraReach API through Jentic.

Why is there no official OpenAPI spec for TerraReach API?

TerraReach does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call TerraReach API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the TerraReach API use?

The TerraReach OpenAPI spec does not declare an HTTP-level securityScheme; live integrations use API keys issued through the /api-keys endpoint and presented per the documented flow. Through Jentic, those keys live in the Jentic vault so the agent never sees the raw secret.

Can I send bulk SMS with the TerraReach API?

Yes. POST /v2/sms/bulk accepts a list of recipients and messages in a single request, and /v1/sms/bulk remains available for clients on the legacy contract. Bulk sends reduce per-message HTTP overhead for broadcasts.

What are the rate limits for the TerraReach API?

Rate limits are not declared in the TerraReach spec. Treat the API as moderate-throughput, batch where possible via the bulk endpoints, and back off on 429 responses. For very large broadcasts, split across multiple bulk calls.

How do I send a single SMS with the TerraReach API through Jentic?

Search Jentic for 'send TerraReach SMS', load the POST /v2/sms operation, and execute it with the recipient number and message body. The API key sits in the Jentic vault throughout, so it never enters the agent's prompt.

Can I top up SMS balance via the TerraReach API?

Yes. POST /payments/stripe processes a Stripe-backed top-up against the account's billing details. This lets a self-service signup flow complete without a separate billing portal.

Docs Terrareach TerraReach API

Connect the TerraReach API to your agent

Capabilities

Start building with TerraReach API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs