Textellent API

Setup

Wiring Textellent by hand means setting its two API-key headers, the authCode and the partnerClientCode, on every request to client.textellent.com and handling errors yourself. Through Jentic you install once, import Textellent from the API Directory, store the keys once, and your agent calls it.

Permission scoping

Textellent puts the contact id in the URL path (/contacts/{contactId}.json), so a rule can pin your agent to one contact for reads. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.

Credential isolation

Your Textellent API keys are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a text message' or 'find a contact by phone number', and Jentic returns the matching Textellent operation with its input schema so the agent calls the right endpoint without browsing the reference docs.