API

API reference

macrocontent exposes several HTTP surfaces. Interactive OpenAPI (Swagger) on the API host is the source of truth for request and response shapes — this handbook explains when to use each API and how to authenticate.

Swagger is canonical

Open the multi-spec explorer: https://api.macrocontent.dev/docs · Raw index: /docs.json · Embedded UI: Swagger in docs

Pick an API

Management

Server automation for one website with mt_ tokens (content, team, domains, activity…).

Content

SDK and prerender content routes with X-Api-Key (pk_ / dk_ / legacy sk_).

Store

Public catalog, bundles, and authenticated library / install routes.

Publisher

Portal session plus /publisher/v1 automation with pt_ tokens.

API surfaces

Spec	Auth	Base	OpenAPI JSON
Management	`mt_ / X-Macro-Token`	`/management`	/docs/specs/management.json
Content	`X-Api-Key / legacy sk_`	`/content`	/docs/specs/content.json
Store	`public + session`	`/store`	/docs/specs/store.json
Publisher	`publisher token / session`	`/publisher`	/docs/specs/publisher.json

Authentication

Different surfaces use different credentials. Start with Authentication for JWT vs X-Api-Key vs mt_ vs publisher tokens — then open Swagger’s green Authorize button for Try it out.

Authorize in Swagger

Authorize only attaches headers to Swagger test calls. It does not log you into Dashboard, Store, or the Publisher portal.

Also see

API tokens (Dashboard)

Create mt_ tokens, presets, rotate and deactivate.

SDK keys

Browser pk_ / dk_ keys for the site SDK.