Powered By Text API

Name: Powered By Text API
Brand: Powered By Text API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingoauth213 EndpointsREST

For Agents

Manage church and nonprofit SMS communication structures including campuses, subscriber groups, opt-in keywords, and message templates. Supports multi-campus organizational hierarchies.

Install Jentic One Beta

Connect the Powered By Text API to your agent

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

Organize multi-campus communication structures with hierarchical organizational units

Create and manage subscriber groups within each campus for targeted messaging

Configure keyword-based opt-in flows for subscriber self-enrollment via text

GET STARTED

Start building with Powered By Text API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Powered By Text API for, with concrete tasks.

★ Multi-Campus Communication Setup

Configure communication infrastructure for churches and nonprofits with multiple locations. The API enables creating organizational units (campuses) under a parent account, each with their own groups, keywords, and templates. This hierarchical structure allows location-specific messaging while maintaining centralized template management and account-level oversight across all campuses.

Create a new campus organizational unit named 'Downtown Campus' via POST /orgunit, then create a subscriber group named 'Youth Ministry' under it

Keyword-Based Subscriber Management

Set up keyword-based opt-in flows where congregation members text a keyword to subscribe to specific groups. The API manages keywords linked to groups under organizational units, enabling self-service enrollment. Members text a keyword (e.g., 'YOUTH') to a short code and are automatically added to the corresponding group for future messages.

List all keywords for the 'Youth Ministry' group using GET /orgunit/{orgunitId}/groups/{groupId}/keywords and verify the expected opt-in keyword is configured

Message Template Management

Create and maintain reusable message templates for recurring communications like event reminders, prayer requests, and announcements. Templates are managed at the account level and can be used across all campuses and groups. The API supports creating, listing, updating, and deleting templates, enabling centralized content management for consistent messaging.

Create a new message template named 'Sunday Service Reminder' with body 'Join us this Sunday at {time}. See you there!' using POST /accounts/{accountId}/templates

AI Agent Church Communication Management

Enable AI agents to manage church and nonprofit messaging infrastructure through Jentic. Agents discover group, keyword, and template management operations via intent search and receive operation schemas for constructing valid requests. Jentic handles OAuth 2.0 token acquisition automatically, enabling agents to focus on communication structure rather than authentication flows.

Search Jentic for 'create a subscriber group for church messaging', load the Powered By Text group creation schema, and execute to add a new ministry group under a campus

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for powered by text api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/accounts/{accountId}

Get account details

POST

/orgunit

Create a new campus organizational unit

GET

/orgunit/{orgunitId}/groups

List groups within a campus

POST

/orgunit/{orgunitId}/groups

Create a new subscriber group

GET

/orgunit/{orgunitId}/groups/{groupId}/keywords

List keywords for a group

GET

/accounts/{accountId}/templates

List message templates

POST

/accounts/{accountId}/templates

Create a new message template

GET

/accounts/{accountId}

Get account details

POST

/orgunit

Create a new campus organizational unit

GET

/orgunit/{orgunitId}/groups

List groups within a campus

POST

/orgunit/{orgunitId}/groups

Create a new subscriber group

GET

/orgunit/{orgunitId}/groups/{groupId}/keywords

List keywords for a group

Why Jentic?

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

Credential isolation

Powered By Text OAuth 2.0 client credentials (client_id and client_secret) are stored encrypted in the Jentic vault (MAXsystem). Token acquisition and refresh are handled automatically — agents never see raw credentials.

Intent-based discovery

Agents search by intent (e.g., 'manage church messaging groups') and Jentic returns matching Powered By Text operations with their input schemas, so the agent can configure communication structures without navigating platform documentation.

Time to first call

Direct Powered By Text integration: 1-2 days for OAuth setup and organizational hierarchy understanding. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Powered By Text API through Jentic.

Why is there no official OpenAPI spec for Powered By Text API?

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

The Powered By Text API uses OAuth 2.0 with the Client Credentials flow. You obtain tokens from https://login.poweredbytext.com/connect/token using your client_id and client_secret. Through Jentic, OAuth token acquisition and refresh are handled automatically by the credential vault.

Can I manage multiple campuses with the Powered By Text API?

Yes. The /orgunit endpoint supports creating multiple organizational units (campuses) under a single account. Each campus can have its own groups, keywords, and messaging structure. Use POST /orgunit to create campuses and PUT /orgunit/{orgunitId} to update existing ones.

What are the rate limits for the Powered By Text API?

Rate limits depend on your account tier with Powered By Text. The API provides both production (api.poweredbytext.com) and sandbox (api-qa.poweredbytext.com) environments. Use the sandbox for development and testing to avoid impacting production rate allowances.

How do I create a subscriber group through the Powered By Text API using Jentic?

Install the SDK with pip install jentic, then search for 'create a messaging group for church'. Jentic returns the POST /orgunit/{orgunitId}/groups operation schema with the required orgunitId path parameter and group name/description body fields. Execute to create the group under a specific campus.

Does the Powered By Text API support message sending directly?

The documented API focuses on organizational structure management (accounts, campuses, groups, keywords, templates) rather than direct message dispatch. Message sending is typically handled through the platform's keyword-triggered and scheduled messaging features configured via groups and templates.

Powered By Text API

Connect the Powered By Text API to your agent

Capabilities

Start building with Powered By Text API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs