Telstra Messaging API v3.x

Setup

Wiring the Telstra Messaging API by hand means running its OAuth2 client-credentials flow to mint scoped tokens, refreshing them, targeting products.api.telstra.com/messaging/v3, and writing the retry glue yourself. Through Jentic you install once, import the Messaging API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

The Messaging API puts the message id in the URL path (/messages/{messageId}), so a rule can pin your agent to one message: it can read and update that message and nothing else. You choose the operations it may call, so ones like provisioning free-trial numbers are not included unless you add them.

Credential isolation

Your Telstra client credentials 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 message' or 'check message status', and Jentic returns the matching Messaging API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.