Build and test your integration.
Use guided requests or any operation from the published OpenAPI. This console talks to this origin’s native API. It creates real tenant resources; provider actions may send messages or incur charges.
Disconnected. Connect an API key to begin.
Connection & tenant
Use an operator-issued backend key for controlled development. Your application must keep it on its backend. Nothing is stored in localStorage, sessionStorage or analytics.
Disconnected. Public reference is available without a key.
Registered connectors and capabilities
Tenants & settings
Choose an API operation
Endpoint details
Advanced request headers and query
Only headers declared by the selected operation. Authorization is managed above.Edit complete request JSON
Request schema
Stopping a request does not undo a committed operation. Reconcile before retrying.
Response body · sensitive fields masked
Run a request to see its response.
Recent request metadata (no payloads)
Browser tools
Backend key stays in this developer page. Inbox reads use a separate grant. Explicitly start an authority lease only for resources you may authorize; it stops on disconnect, tenant switch, expiry or refresh.
No inbox snapshot.
System notifications
The permission test displays a local notification only. Real Web Push must pass the native push-config check and have VAPID plus a server-to-server authority configured; fake mode never pretends to deliver push.
To send through the service, publish an inbox notification with push:true using the request
above. Messages are generic; resource content is read through the authorized inbox.