mt_server
Interactive: Swagger · Management · JSON: /docs/specs/management.json
resource:action rules in Dashboard → API Tokens before calling routes. When to use
- CI/CD content sync, publish, or export
- Provisioning domains, webhooks, or data sources from scripts
- Assigning Store components during site bootstrap
- Anything that must not embed browser SDK keys
Base URL & identity
Base: https://api.macrocontent.dev/management
/management/whoamimt_Any valid token — returns identity and platformWebsiteId. Start here to verify auth.
curl -sS https://api.macrocontent.dev/management/whoami \
-H "X-Macro-Token: mt_..."Common endpoint groups
/management/content/nodesmt_List content nodes. Needs content.nodes:read (content_automation preset).
/management/content/values/:nodeIdmt_Write draft values. Needs content.values:write.
/management/content/versions/:id/publishmt_Publish a version. Needs content.versions permissions.
/management/activitymt_Audit timeline with filters (q, from, to, apiTokenId, …). Needs activity:read.
/management/store/*mt_Store component install helpers. Needs store.components:* (see permission catalog).
/management/proxy/*mt_API Proxy connections, routes, call log. Needs proxy.* permissions (connect_automation preset).
/management/identitymt_Identity Assertion status / JWKS metadata. Needs identity:read.
/management/webhooksmt_Website webhooks CRUD. Needs settings.webhook:* (was unmounted — now on Management API).
read_only, content_automation, data_automation, connect_automation, team_manager, full_admin (*:*). Details in API tokens and Authentication.