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

# Android Texter API

The Android Texter API sends and receives SMS through a user's own linked Android phones rather than a carrier gateway. It broadcasts outbound messages, lists received messages, reports delivery status for a sent message, and returns the conversation history for a phone number. Around messaging it manages contacts, quick replies, linked devices, spam flagging, and webhooks that push inbound events to your own endpoint.

## For AI agents

Send SMS broadcasts and read replies through linked Android devices, check delivery status and conversation history, and manage contacts, quick replies, and inbound webhooks.

## Scope

Does not handle email, voice calls, or push notifications. Use for SMS messaging through linked Android devices only.

## Capabilities

- Send an SMS broadcast through a linked Android device
- List received messages and read the history for a phone number
- Check the delivery status of a sent message
- Store and upsert contacts for messaging
- Register webhooks that push inbound SMS events to your endpoint
- Flag and unflag a phone number as spam

## Use cases

### Agent-sent SMS from a linked phone

An AI agent connected through Jentic sends a text to a customer through the user's own linked Android device and then confirms it landed. It broadcasts the message, reads back delivery status, and can pull the conversation history to see the reply. Because the agent finds operations by intent, outbound texting works without a developer wiring the device and messaging endpoints by hand.

Example prompt: Send a broadcast message to one phone number, then check its delivery status and return the conversation history for that number

### Two-way SMS with inbound webhooks

To handle replies, the API registers a webhook that pushes inbound messages to your endpoint as they arrive. An agent can create the webhook, then react to each incoming text, for example by sending a quick reply. This supports conversational SMS flows where the agent responds to customers rather than only blasting one-way messages.

Example prompt: Register a webhook for inbound messages, then list received messages and send a quick reply to the latest one

### Contact and spam management

The API keeps a contact list and a spam list so messaging stays organized. An agent can upsert a contact before messaging, and flag or unflag a phone number as spam to filter unwanted threads. This keeps outbound sends targeted and inbound noise under control without manual list upkeep.

Example prompt: Upsert a contact with a name and phone number, then flag a different number as spam

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/messages/broadcast` | Send an SMS broadcast |
| GET | `/messages/received` | List received messages |
| GET | `/v1/messages/status/{id}` | Get delivery status for a message |
| GET | `/v1/messages/history/{phone}` | Get conversation history for a phone |
| POST | `/contacts` | Create or upsert a contact |
| GET | `/v1/devices` | List linked Android devices |
| POST | `/v1/webhooks` | Register a webhook for inbound events |

## Key resources

- **Messages** — Send broadcasts, list received messages, and read delivery status and history
- **Contacts** — List and upsert contacts used for messaging
- **Devices** — List the Android phones linked to the account
- **Quick Replies** — Create, update, and delete reusable quick replies
- **Webhooks** — Register and remove webhooks for inbound SMS events
- **Spam** — Flag and unflag phone numbers as spam

## 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:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 23 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 84 / 100
- **View full report:** https://jentic.com/apis/androidtexter.com/androidtexter/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 the Android Texter API by hand means choosing between its X-API-Key and bearer-JWT auth, linking a device, and handling inbound webhooks yourself. Through Jentic you install once, import the API from the Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Android Texter API carries its targets in the request body, so rules bound which operations your agent may call: you can allow message sends and delivery-status reads while leaving device management and webhook deletion out unless you add them. You choose the operations it may use.
- **Credential handling:** Your Android Texter 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.
- **Discovery method:** Agents search Jentic by intent such as 'send a text message' or 'check delivery status', and Jentic returns the matching Android Texter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Twilio sends SMS over a carrier-grade messaging platform rather than through your own linked Android phones
- **Telnyx** — Telnyx offers programmable SMS and voice over its own carrier network
- **MessageBird SMS** — MessageBird sends SMS internationally through a cloud communications platform

## FAQ

### What authentication does the Android Texter API use?

The Android Texter API authenticates with an API key sent in the X-API-Key header, or a bearer JWT sent in the Authorization header, as declared in its OpenAPI spec. Through Jentic the credential is stored once by your own self-hosted instance and injected at call time, so it never appears in the agent's prompt or logs.

### Can I send and receive text messages with the Android Texter API?

Yes. You broadcast outbound SMS through a linked Android device, list received messages, and read the conversation history for a phone number. Registering a webhook pushes inbound messages to your endpoint so an agent can reply in near real time.

### Is there an Android Texter API MCP server?

You do not need an MCP server to give your agent the Android Texter API. Jentic connects it directly from the API Directory: import the API, store your API key once, and your agent sends and reads messages on demand without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only the message-send and delivery-status read operations, so the agent can text and confirm delivery but cannot delete webhooks or manage devices unless you add those, and every call it makes is logged for review. The Android Texter API carries its targets in the request body, so rules bound which operations the agent may call.

### What are the rate limits for the Android Texter API?

The OpenAPI spec does not specify rate limits for the Android Texter API, and throughput also depends on the linked Android device. Check the vendor documentation at https://androidtexter.com for current limits before sending large broadcasts.

### How do I send a text with the Android Texter API through Jentic?

Search Jentic for an intent such as 'send an SMS broadcast', and it returns the matching operation with its input schema so your agent passes the number and message correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.