One API for trusted customer actions.
A small set of calls that cover authentication, approval and authorization across every channel. This page explains the concepts; the reference, keys and guides live in the Assure developer portal.
What does the Assure API do?
It lets your software ask a real person a precise question — are you who you say you are, and do you approve this action — in a channel that customer already trusts, and returns the answer to your systems. Authentication is available in preview form today; approval and authorization calls are not built yet, and no endpoint names on this page are shipping endpoints.
Four things to ask a customer.
We describe the shape openly so teams can evaluate the direction before anything ships.
Verify a customer
Ask Assure to establish that the person on the other end is really your customer, in a channel they already trust, and get the outcome back.
Request an approval
Send the exact action — an amount, a change, a release of information — and capture an explicit approve or decline from the customer.
Check what was approved
Look up what was shown to the customer and what they decided, so your own systems can act on a recorded answer rather than an assumption.
Escalate to a human
Hand a conversation to a person with the identity and approvals already obtained, instead of starting the trust conversation over.
Conceptual calls, named plainly.
Names only — no request or response bodies here. The live reference is in the developer portal.
authenticate()Ask the customer to prove who they are.requestApproval()Present a specific action and capture the answer.verifyAuthorization()Check what was approved, and when.sendChallenge()Issue a step-up challenge on the right channel.requestPayment()Ask the customer to authorize an amount.escalateToHuman()Hand the conversation to a person with context.These names are conceptual and are not shipping endpoints. Current API keys, references and integration guides live in the Assure developer portal.
Standard connections, not a bespoke bridge.
Described conceptually. Only the MCP tool surface on this site is live today.
REST
Ordinary authenticated HTTP requests from your own service logic. No SDK required to get started.
Webhooks
Receive outcomes — approved, declined, expired — as events your systems can react to.
OAuth 2.0 and OpenID Connect
Designed to fit the token and identity flows your platform already speaks, rather than replacing them.
MCP
Assure context is already exposed as tools an AI assistant can call. Authorization as a tool is a later step.
Alongside the identity system you already run.
Assure is designed to add the customer-facing verification and approval moment, not to replace your identity provider or CIAM.
The integration concepts are the standard ones: a step-up request during a login flow, an assurance step during account recovery, a confirmation before a high-risk change, and an outcome signal sent back to your identity platform. Compatibility is expressed through open standards — OAuth 2.0, OpenID Connect, REST and webhooks, with FIDO2, WebAuthn and the NIST digital identity guidelines informing the design. No certification is claimed, and no identity vendor is claimed as a partner or a built integration.
Identity providers →A verified decision from inside a service conversation.
An enterprise agent calls Assure with a proposed action; Assure authenticates the customer, captures approve or decline, and returns the outcome. This is not built today.
Salesforce, Agentforce and Service Cloud are trademarks of Salesforce, Inc. No partnership, endorsement, certification or AppExchange listing is claimed or implied.
What an agent can do today, and what comes next.
We separate the two deliberately, because the difference matters when you are deciding what to build on.
Reading Assure context
This site exposes an MCP tool surface, so an AI client can ask what Assure is, which channels are described, estimate messaging savings, and pass along a sales enquiry. It answers questions — it does not authorize anything.
Authorization as a tool
The intended next step: an agent calls a tool that asks a real person to approve a specific action, and receives that decision back. No agent authorization, scoped authorization or authorization record exists in the product today.
AI agent authorization →What you can run today.
A developer sandbox with test credentials and simulated outcomes is in development.
In the meantime, the verification experience on this site is a clearly labelled simulation: the codes, the expiry and the STOP, START and HELP replies all run in the browser with a fictitious number, and no messaging provider is connected. It is there to show the customer experience, not to stand in for an API.
Try the verification simulation →Frequently asked.
Authentication for today. Authorization for what's next.
Start in the developer portal, or talk to us about the moments your product needs a real person to approve.