Docs
Swagger

API · Management

Management API

Server automation for a single website with granular mt_ tokens — content, team, domains, assets, webhooks, activity, and store installs.

mt_server

Interactive: Swagger · Management · JSON: /docs/specs/management.json

Default deny
New tokens start with zero permissions. Grant a preset or explicit 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

GET/management/whoamimt_

Any valid token — returns identity and platformWebsiteId. Start here to verify auth.

bash
curl -sS https://api.macrocontent.dev/management/whoami \
  -H "X-Macro-Token: mt_..."

Common endpoint groups

GET/management/content/nodesmt_

List content nodes. Needs content.nodes:read (content_automation preset).

PUT/management/content/values/:nodeIdmt_

Write draft values. Needs content.values:write.

PATCH/management/content/versions/:id/publishmt_

Publish a version. Needs content.versions permissions.

GET/management/activitymt_

Audit timeline with filters (q, from, to, apiTokenId, …). Needs activity:read.

GET/management/store/*mt_

Store component install helpers. Needs store.components:* (see permission catalog).

Presets
read_only, content_automation, data_automation, team_manager, full_admin (*:*). Details in API tokens and Authentication.