TextBee SMS Gateway

Name: TextBee SMS Gateway API
Brand: TextBee SMS Gateway
Availability: InStock

✓ Official Vendor SpecCommunicationsSms MessagingapiKey2 EndpointsREST

For Agents

Programmatically send sms, get message history. Covers 2 operations with apiKey authentication.

Install Jentic One Beta

Connect the TextBee SMS Gateway to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TextBee SMS Gateway, 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%2Ftextbee.dev%2Ftextbee-dev" | 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%2Ftextbee.dev%2Ftextbee-dev" | 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 TextBee SMS Gateway API.

Send SMS

Get message history

Integrate TextBee SMS Gateway into automated workflows

Query and filter TextBee SMS Gateway records by parameters

GET STARTED

Start building with TextBee SMS Gateway API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use TextBee SMS Gateway API for, with concrete tasks.

★ Communications Operations

Use the TextBee SMS Gateway to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including send sms, get message history.

Call POST /gateway/devices/{deviceId}/send-sms to send sms

Data Retrieval and Monitoring

Query TextBee SMS Gateway resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary TextBee SMS Gateway endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call TextBee SMS Gateway 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 sms', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — turn your android phone into a powerful sms gateway.

METHOD

PATH

DESCRIPTION

POST

/gateway/devices/{deviceId}/send-sms

Send SMS

GET

/gateway/devices/{deviceId}/messages

Get message history

POST

/gateway/devices/{deviceId}/send-sms

Send SMS

GET

/gateway/devices/{deviceId}/messages

Get message history

Why Jentic?

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

Setup

Wiring the TextBee SMS Gateway by hand means learning its x-api-key header auth against the api.textbee.dev/api/v1 host and coding each device send and message-read call yourself. Through Jentic you install once, import the TextBee SMS Gateway from the API Directory, store the API key once, and your agent calls it.

Permission scoping

TextBee puts the device id in the URL path (/gateway/devices/{deviceId}/send-sms), so a rule can pin your agent to one device: it can send and read messages for that device and nothing else. You choose the operations it may call, so sending is not included unless you add it.

Credential isolation

Your TextBee API key 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 'send an SMS from a device' or 'read received messages', and Jentic returns the matching TextBee SMS Gateway operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TextBee SMS Gateway API through Jentic.

What authentication does the TextBee SMS Gateway use?

The TextBee SMS Gateway uses an API key passed in the `x-api-key` 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 sms with the TextBee SMS Gateway?

Yes. Use the POST /gateway/devices/{deviceId}/send-sms endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the TextBee SMS Gateway?

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 sms through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send sms'. Jentic returns the matching TextBee SMS Gateway operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the TextBee SMS Gateway have?

The TextBee SMS Gateway exposes 2 endpoints covering gateway operations.

TextBee SMS Gateway

Connect the TextBee SMS Gateway to your agent

Capabilities

Start building with TextBee SMS Gateway API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs