Scoped API keys instead of user passwords
Included where the workspace plan, connected account and provider permissions allow it.
Connect existing operational screens or approved APIs to conversation workflows, and use scoped MirageCHAT API keys and webhooks for supported capabilities.
What it includes
Webhooks for supported real-time events
Included where the workspace plan, connected account and provider permissions allow it.
Embedded operational panels inside conversations
Included where the workspace plan, connected account and provider permissions allow it.
Documented messaging and channel-management endpoints
Included where the workspace plan, connected account and provider permissions allow it.
How to use it
- Choose an embedded screen or API integration based on the system you already have.
- Grant only the accounts and teammates that need access.
- Use the authenticated developer manual for the exact supported contract.
Availability is measured per account. MirageCHAT shows when a provider permission or account step is still required; it does not label that capability as active.
Frequently asked questions
Is every internal function a public endpoint?
No. The supported public contract is the authenticated API manual; access also depends on plan, module and scope.
Can I resell an integration?
Reseller use is supported where contracted and enabled. Branding, limits and commercial terms must be agreed for that account.