Updox Patient Communications API

Setup

Wiring the Updox Patient Communications API by hand means sending your key in the appAuth header on every call, matching each RPC-style operation to its request body, and handling responses yourself. Through Jentic you install once, import the Updox Patient Communications API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Updox API is RPC-style and carries its targets in the request body, so scope your agent to the operations it needs, such as listing or searching the address book. You choose the operations it may call, so a write like creating a contact is not included unless you add it.

Credential isolation

Your Updox API key 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 'search the address book' or 'ping the server', and Jentic returns the matching Updox Patient Communications API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.