Ghost

This connector uses the Ghost Admin API v5 (ghost.org/docs/admin-api/).

Setup:

1. Sign in to Ghost Admin → Settings → Advanced → Integrations → Add custom integration.
2. Copy the Admin API Key — format is <id>:<secret> (e.g. 5f3a...c4:b9d8...e2).
3. Set:
   • GHOST_ADMIN_API_URL = your Ghost site's admin API base, e.g. https://yoursite.com/ghost/api/admin
   • GHOST_ADMIN_API_KEY = the full id:secret key from step 2

Authentication — JWT generation required: Ghost's Admin API does NOT accept the raw API key. Each request needs a JWT signed with the secret half. The JWT is short-lived (5 min) and has these claims:

  alg: 'HS256', kid: <id_part>, typ: 'JWT'
  exp: now+5min, iat: now, aud: '/admin/'

This connector currently expects the OPERATOR or external orchestrator to generate the JWT and pass it as GHOST_ADMIN_JWT — the engine then sends Authorization: Ghost ${GHOST_ADMIN_JWT}. For a proper LOGIN_TOKEN-style auto-rotation see the Sorare adapter as the reference pattern; that's a future enhancement.

Workaround for testing: use the official @tryghost/admin-api JS SDK to generate a JWT and copy it as GHOST_ADMIN_JWT. Or use the Ghost CLI: ghost generate-jwt.

Content API alternative: for read-only public-published content, the simpler Content API uses a single key as a query parameter — no JWT. Switch baseUrl to /ghost/api/content and use a Content API key.

Post status: draft, published, scheduled, sent.

Mobiledoc vs Lexical: Ghost stores post content in either format. Modern Ghost (v5+) defaults to Lexical (lexical field). Set html on writes — Ghost converts to its internal format.

Pagination: ?page=N&limit=M (max 100 for posts/pages, 15 for some). Response has meta.pagination.

Webhooks out of scope.

Out of scope here: themes, settings, redirects management, oEmbed.