Text In Church API

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 isolation

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.

Intent-based discovery

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.