Scoped API keys
Use a purpose-specific key instead of a teammate password. Access remains limited by workspace, plan, module and granted scope.
Developer platform
A factual overview of MirageCHAT API access, scoped keys, webhooks, supported messaging operations and the authenticated developer manual.
Create a workspaceUse a purpose-specific key instead of a teammate password. Access remains limited by workspace, plan, module and granted scope.
Messaging, contacts and selected WhatsApp and Instagram management operations are available where documented and permitted.
Receive supported real-time events without polling. Consumers must verify, deduplicate and retry safely.
The authenticated developer manual inside MirageCHAT is the canonical list of endpoints, fields and permissions. This public page intentionally does not promise that every internal screen is a public endpoint.
An existing operational screen can open inside a conversation with approved context. A system with an API can instead be mapped into a purpose-built panel. Keep provider credentials server-side and grant access only to the accounts and teammates that need it.