API and webhooks
Your systems can talk to Magic Dashboard in two ways:
- through the API, which reads and changes the organization's data — portal users, entities, connectors, pages and the rest of what the dashboard shows;
- through webhooks, which notify your system the moment something happens, without it having to ask.
All of this lives in System › API (/dashboard/api), in four tabs:
| Tab | What you find |
|---|---|
| API Tokens | Where to create the token your applications use on the API. See API tokens. |
| Webhooks | The endpoints that receive events and the history of each delivery. See Webhooks and Deliveries. |
| Rate Limits | How many requests the API accepts. See Rate limiting. |
| Documentation | Shortcuts to the API documentation, the OpenAPI specification, the Postman collection and the webhook payload examples. |
To open this screen, your role needs access to API tokens (see Members). Without it, the dashboard shows an access denied notice.
Workspace in API calls
The token identifies the organization. The workspace goes in the X-Workspace-Id header, with the ID shown on each card in System › Workspaces. While the organization has a single workspace, the header is optional; from the second one on, every call must say which workspace it acts on. See Organization and workspaces.
In this section
- API tokens — how your applications authenticate on the API.
- Webhooks — register, test and protect the endpoints that receive events.
- Deliveries — follow each delivery and resend what failed.
- Webhook events — the payload format and the available events.
- Rate limiting — the request limits and what happens when you exceed them.
The full endpoint reference is in the API section of the top menu (start with the introduction), and the tools for AI agents are in the MCP section.