Publish articles and creator-hub posts via HTTPS.

Every request must include an Authorization header carrying a bearer token. The token is set on the server as the PUBLISH_API_KEY environment variable; ask your MarketScale contact for the value.

Authorization: Bearer <PUBLISH_API_KEY>

Requests without a token (or with the wrong token) return 401. If the server has no PUBLISH_API_KEY configured at all, every request returns 503 until it's set.

POST /api/publish/article: write an article into one of the 16 industry collections.

* required

Request

curl -X POST https://marketscale.com/api/publish/article \
  -H "Authorization: Bearer $PUBLISH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "collection": "healthcare",
    "title": "Inside the new specialty-pharmacy model",
    "excerpt": "How a specialty pharmacy aligns patients, providers, and payers.",
    "author": "Lea Sims",
    "content": "Opening paragraph.\n\nSecond paragraph.",
    "featuredImageUrl": "https://example.com/cover.jpg",
    "videoUrl": "https://studio.marketscale.com/exports/sp-model.mp4",
    "tags": ["specialty-pharmacy", "value-based-care"]
  }'

Response

{
  "status": "created",
  "id": "67df9b4a3c1a9f6f8e2b1d34",
  "slug": "inside-the-new-specialty-pharmacy-model",
  "collection": "healthcare",
  "url": "https://marketscale.com/industries/healthcare/inside-the-new-specialty-pharmacy-model"
}

Re-posting the same slug returns "status": "updated" with 200 instead of 201. The response also carries contentSource: "provided" when your article was kept and enriched, "generated" when MarketScale wrote it.

POST /api/publish/channel-post: write a post that surfaces under a specific creator hub (Show). The hub is identified by its channelId, which you set on the Show record in Payload admin.

* required

Request

curl -X POST https://marketscale.com/api/publish/channel-post \
  -H "Authorization: Bearer $PUBLISH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channelId": "tekniplex-prod",
    "title": "IPS Global Sales Meeting · day three",
    "excerpt": "Three days of cross-regional collaboration in Mexico City.",
    "author": "Jane Smith",
    "content": "Opening paragraph.\n\nSecond paragraph.",
    "featuredImageUrl": "https://example.com/cover.jpg",
    "videoUrl": "https://studio.marketscale.com/exports/ips-day-three.mp4",
    "tags": ["sales", "global"]
  }'

Response

{
  "status": "created",
  "id": "67df9b4a3c1a9f6f8e2b1d34",
  "slug": "ips-global-sales-meeting-day-three",
  "channelSlug": "tekniplex",
  "channelName": "TekniPlex",
  "collection": "business-services",
  "url": "https://marketscale.com/industries/business-services/ips-global-sales-meeting-day-three",
  "hubUrl": "https://marketscale.com/creator-hubs/tekniplex"
}

The post lives inside the show's industry collection but carries the show's channelName, so it appears on both the industry feed and the creator hub. Hub pages are revalidated on publish, so the post is visible at hubUrl immediately.

Idempotency is scoped to the hub: re-posting a slug updates the post only when it belongs to the same hub. A slug owned by another hub is never overwritten; the new post gets a suffixed slug instead. If the Show has no industry set, the response includes a warning and the post is stored under business-services.