Docs
Swagger

API · Publisher

Publisher API

Publisher portal session routes under /publisher/me and automation under /publisher/v1 with pt_ tokens.

JWTPublisher

Interactive: Swagger · Publisher · JSON: /docs/specs/publisher.json

Two layers
The portal UI uses a JWT session on /publisher/me. Long-lived scripts use publisher API tokens (pt_…) on /publisher/v1 with X-Macro-Publisher-Token. See Authentication.

When to use

  • Automate listing create/patch and bundle validation in CI
  • Sync listing metadata from an internal catalog
  • Read whoami / permission catalog for token diagnostics

Automation base

Base: https://api.macrocontent.dev/publisher/v1

GET/publisher/v1/whoamiPublisher

Any valid publisher token — verify identity and scope.

GET/publisher/v1/listingsPublisher

List your listings. Needs publisher.listings:read.

POST/publisher/v1/listings/validate-bundlePublisher

Run Macro Score / validation without relying on a failed persist. Needs listings:write.

POST/publisher/v1/listingsPublisher

Create a listing (bundle must pass validation). Needs publisher.listings:write.

PATCH/publisher/v1/listings/:idPublisher

Update listing metadata or bundle. Paid offers require active Stripe Connect.

Paid listings
Without stripeConnectStatus === 'active', paid offers fail with STRIPE_REQUIRED. Connect from the portal Payouts page.
bash
curl -sS https://api.macrocontent.dev/publisher/v1/whoami \
  -H "X-Macro-Publisher-Token: pt_..."

Product guides: Listings · Bundles & score.