MojoTxt API

Name: MojoTxt API API
Brand: MojoTxt API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbasic8 EndpointsREST

For Agents

Manage SMS subscriber lists, send broadcast messages from owned phone numbers, and pull message and donation logs from MojoTxt.

Connect the MojoTxt API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MojoTxt 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.

Install Jentic One Beta (Self-Hosted)

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

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 MojoTxt API API.

List phone numbers owned by the MojoTxt account

Add or remove subscribers on a specific phone number's list

Send broadcast SMS messages from a phone number to its subscribers

Retrieve historical message logs for a phone number

GET STARTED

Start building with MojoTxt API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for MojoTxt API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for MojoTxt API, keeping it validated and agent-ready. MojoTxt is an SMS messaging platform focused on subscriber list management, broadcast sending, and donation tracking, often used by nonprofits and small organizations running text-to-give and text-to-subscribe campaigns. The API exposes operations to manage phone numbers, add or remove subscribers, send messages to a list, and pull message and donation logs. It is positioned as a turnkey SMS engagement tool rather than a generic SMS gateway.

Use Cases

Patterns agents use MojoTxt API API for, with concrete tasks.

★ Nonprofit Text-to-Give Campaign Tracking

Pull donation records associated with a MojoTxt phone number to reconcile fundraising totals against finance ledgers. The donations endpoint exposes individual contribution records linked to the originating subscriber, removing manual export steps from the donation reporting workflow. Suitable for nonprofit operations teams running monthly board reports on text-to-give performance.

Call GET /{phone_number}/donations/list for the campaign number to retrieve the month's donation records and aggregate them into a fundraising total.

Subscriber List Maintenance

Programmatically add new opt-ins captured from a website form to a MojoTxt subscriber list and remove unsubscribed contacts to keep the list compliant. The add and remove endpoints take a subscriber identifier and the target phone number, so a CRM or signup form can sync state without manual import. Practical for organizations replacing manual CSV uploads with real-time syncing.

Call POST /{phone_number}/subscribers/add with the new contact's phone number when a website opt-in form is submitted.

Broadcast SMS Sending

Send a message from a MojoTxt-owned phone number to its subscriber list using the messages endpoint, then pull the message log to confirm delivery. This pattern works for event reminders, advocacy alerts, or weekly newsletters where the target audience has already opted in. The single-call broadcast model is simpler than building per-recipient send loops on top of generic SMS gateways.

Call POST /{phone_number}/messages/send with the message body to broadcast to all subscribers, then GET /{phone_number}/messageLog/list to confirm delivery.

Agent-Driven Constituent Outreach

AI agents managing supporter outreach for nonprofits or advocacy groups call MojoTxt through Jentic to send timely SMS broadcasts and pull engagement data without holding the basic-auth credential in their context. Jentic's spec is the only structured definition for MojoTxt, so schema-driven agents rely on Jentic for tool selection and parameter shape.

Search Jentic for 'broadcast an sms to my subscribers', load POST /{phone_number}/messages/send, and execute with the campaign body.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/phoneNumbers/list

List MojoTxt phone numbers on the account

GET

/{phone_number}/subscribers/list

List subscribers for a phone number

POST

/{phone_number}/subscribers/add

Add a subscriber to a phone number list

POST

/{phone_number}/subscribers/remove

Remove a subscriber from a phone number list

POST

/{phone_number}/messages/send

Send a broadcast SMS to a phone number's subscribers

GET

/{phone_number}/messageLog/list

Retrieve message history for a phone number

GET

/{phone_number}/donations/list

List donations received via a text-to-give number

GET

/phoneNumbers/list

List MojoTxt phone numbers on the account

GET

/{phone_number}/subscribers/list

List subscribers for a phone number

POST

/{phone_number}/subscribers/add

Add a subscriber to a phone number list

POST

/{phone_number}/subscribers/remove

Remove a subscriber from a phone number list

POST

/{phone_number}/messages/send

Send a broadcast SMS to a phone number's subscribers

Why though Jentic?

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

Credential isolation

MojoTxt basic-auth credentials are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Agents never see the username or password.

Intent-based discovery

Agents search by intent (e.g., 'send a broadcast sms') and Jentic returns the matching MojoTxt messages or subscribers operation with its parameter schema.

Time to first call

Direct integration: 4-8 hours to wire up basic auth, list management, and broadcast send. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Messaging API

General-purpose programmable SMS, MMS, and WhatsApp gateway with global coverage

Choose Twilio when the workflow needs raw per-recipient SMS sending, two-way conversations, or international reach; use MojoTxt for opt-in subscriber list broadcasts and text-to-give.

Alternative

Plivo Messaging API

Programmable SMS and voice platform with subscriber-style messaging features

Choose Plivo for a developer-focused SMS gateway with global numbers; MojoTxt is purpose-built for opt-in subscriber broadcasts.

Complementary

ClickSend SMS API

Multi-channel messaging API covering SMS, MMS, voice, and post mail

Use ClickSend alongside MojoTxt to extend campaigns into postal mail or voice broadcasts when SMS alone is not enough.

FAQs

Specific to using MojoTxt API API through Jentic.

Why is there no official OpenAPI spec for MojoTxt API?

MojoTxt does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MojoTxt 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 MojoTxt API use?

MojoTxt uses HTTP Basic authentication — the account username and password (or API credential pair) are sent in the Authorization header as a base64-encoded basicAuth challenge. Through Jentic, the credential pair is held in the encrypted vault and injected at request time so the secret never enters the agent's context.

Can I send a broadcast SMS with the MojoTxt API?

Yes. POST /{phone_number}/messages/send takes the broadcast body and dispatches it to every subscriber on that phone number's list. Pull GET /{phone_number}/messageLog/list afterwards to confirm what was sent and to whom.

What are the rate limits for the MojoTxt API?

MojoTxt does not document rate limits in this OpenAPI spec. Carrier-level limits on outbound SMS will apply for broadcast operations, so check https://mojotxt.com or the account dashboard for current send-rate guidance before running large campaigns.

How do I add a subscriber through Jentic?

Run pip install jentic, search for 'add a subscriber to my sms list', load POST /{phone_number}/subscribers/add, and execute it with the target phone number and subscriber details. Jentic returns the operation result so the agent can confirm the opt-in was recorded.

Does MojoTxt support text-to-give donation tracking?

Yes. GET /{phone_number}/donations/list returns donation records linked to the campaign phone number, including the originating subscriber and amount. This makes it straightforward to reconcile text-to-give revenue against finance reports.