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

# Text In Church API

Text In Church messaging and contact management API for church communications, including messaging, contacts, groups, calls, workflows, and connect cards. The API exposes 46 endpoints secured with bearer authentication.

## For AI agents

Programmatically get account details, create or update account metadata. Covers 46 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Get account details
- Create or update account metadata
- Delete account metadata
- Query and filter Text In Church API records by parameters
- Monitor Text In Church API operational status and events

## Use cases

### CRM Operations

Use the Text In Church API to perform crm operations programmatically. The API provides 46 endpoints covering core functionality including get account details, create or update account metadata, get account metadata.

Example prompt: Call GET /account.php to get account details

### Automated Account Management

Automate account operations by combining multiple Text In Church API endpoints. Agents can create or update account metadata and then get account metadata in a single workflow.

Example prompt: Call POST /accountMeta.php to create or update account metadata, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Text In Church API 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 bearer tokens manually.

Example prompt: Search Jentic for 'get account details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/account.php` | Get account details |
| POST | `/accountMeta.php` | Create or update account metadata |
| GET | `/accountMeta.php` | Get account metadata |
| DELETE | `/accountMeta.php` | Delete account metadata |
| POST | `/contact.php` | Create or update a contact |
| GET | `/contact.php` | Get contacts |
| DELETE | `/contact.php` | Delete a contact |
| POST | `/contactComment.php` | Create a contact comment |

## Key resources

- **Account** — Account management
- **Contacts** — Contact management
- **Messages** — Messaging and conversations
- **Groups** — Group management
- **Calls** — Call management

## 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:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 37 / 100
- **View full report:** https://jentic.com/apis/textinchurch.com/textinchurch/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 Text In Church by hand means learning its bearer auth against api.textinchurch.com and threading the token through every contact and account request yourself. Through Jentic you install once, import Text In Church from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Text In Church addresses contacts and account records through operations on endpoints like /contact.php and /accountMeta.php, so limit the agent to the operations it needs, such as reading account details or adding a contact. You choose that set, so destructive operations like deleting a contact are not included unless you add them.
- **Credential handling:** Your Text In Church token 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 'get account details' or 'add a contact', and Jentic returns the matching Text In Church operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Text In Church API use?

The Text In Church API uses a Bearer token in the Authorization 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 get account details with the Text In Church API?

Yes. Use the GET /account.php endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Text In Church API?

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 get account details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account details'. Jentic returns the matching Text In Church API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Text In Church API have?

The Text In Church API exposes 46 endpoints covering account, contacts, messages operations.

### Can I limit what my agent is allowed to do with the Text In Church API?

Yes. Because you run Jentic One yourself, you decide which Text In Church operations your agent can call, and your own rules govern which credentials it uses. You can allow read-only calls such as getting account details from GET /account.php or reading contacts, while withholding writes to /accountMeta.php or /contact.php. Destructive operations like deleting a contact stay off limits unless you explicitly add them to the agent's allowed set.