Ghost Content API

Name: Ghost Content API API
Brand: Ghost Content API
Availability: InStock

✓ Official Vendor SpecMarketingContent ManagementapiKey14 EndpointsREST

For Agents

Read posts, pages, authors, tags, tiers, and site settings from a Ghost publication across 14 endpoints with read-only API-key authentication.

Quickstart

Get started with Ghost Content API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list the latest posts from a ghost publication"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Ghost Content API API.

List published posts with filtering, ordering, and field inclusion

Retrieve a single post by id or by slug for canonical URL resolution

List and look up static pages such as About or Contact

Read author profiles and the posts associated with each author

GET STARTED

Start building with Ghost Content API API

Explore with Jentic

View OpenAPI Document

The Ghost Content API is the read-only public surface of a Ghost publishing site. Across 14 endpoints it exposes posts, pages, authors, tags, tiers, and site settings, with both list and lookup-by-id and lookup-by-slug variants for each major resource. Authentication is an apiKey passed as a query parameter, scoped to read access — write operations live in the separate Ghost Admin API. The Content API is the right surface for headless front ends, mobile apps, and aggregators that render published Ghost content.

Use Cases

Patterns agents use Ghost Content API API for, with concrete tasks.

★ Headless Front-End for a Ghost Site

Teams running Ghost as the CMS but rendering the front end in Next.js, Astro, or another framework use the Content API to fetch posts, pages, and metadata at build or request time. The list endpoints support filtering by tag and author so the front end can build category and author archives without indexing the full content set.

List the latest 10 posts including their tags and author, then render them as a homepage feed.

Mobile App Reader

Mobile apps that show a publication's articles to subscribers fetch posts and pages from the Content API, cache them locally, and render with native typography. The /tiers endpoint exposes membership levels so the app can gate premium content rendering against the user's subscription state determined elsewhere.

Fetch the 50 most recent posts and the tier list, then cache them for offline reading.

Newsletter and Aggregator Feeds

Aggregators and newsletter tools poll the Ghost Content API for new posts on a schedule and fan them out to other channels. Filter by published_at to fetch only posts since the last poll, and use the slug-lookup endpoint to deep-link back to the canonical post URL on the Ghost site.

List posts published in the last 24 hours and post their titles and links to a Slack channel.

AI Agent Content Discovery

An AI agent answering questions about a Ghost publication can search posts and pages by tag or slug, retrieve full content including author and tag metadata, and cite the canonical URL. Through Jentic the agent finds the right list or lookup endpoint by intent and the Content API key stays in the encrypted vault.

List posts tagged 'pricing' and return the title, slug, and excerpt of each.

Key Endpoints

14 endpoints — the ghost content api is the read-only public surface of a ghost publishing site.

METHOD

PATH

DESCRIPTION

GET

/posts/

List published posts

GET

/posts/{id}/

Retrieve a post by id

GET

/posts/slug/{slug}/

Retrieve a post by slug

GET

/pages/

List static pages

GET

/authors/

List authors

GET

/tags/

List tags

GET

/tags/slug/{slug}/

Retrieve a tag by slug

GET

/posts/

List published posts

GET

/posts/{id}/

Retrieve a post by id

GET

/posts/slug/{slug}/

Retrieve a post by slug

GET

/pages/

List static pages

GET

/authors/

List authors

GET

/tags/

List tags

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Ghost Content API keys are stored encrypted in the Jentic vault. Agents receive a scoped invocation capability — the raw key never enters the agent's context, which is meaningful because the key rides in the URL query string and would otherwise leak to logs.

Intent-based discovery

Agents search by intent (e.g. 'list ghost posts' or 'get a ghost post by slug') and Jentic returns the matching operation with its full query-parameter schema for direct execution.

Time to first call

Direct Ghost Content API integration including key handling, caching, and slug resolution: half a day to one day. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sanity

Sanity is a structured-content headless CMS with flexible schemas; Ghost is opinionated for publications

Use Sanity for arbitrary structured content; choose Ghost when the content is articles, pages, and authors

Alternative

Contentful

Contentful is a structured-content headless CMS; Ghost is opinionated for publications and newsletters

Use Contentful for arbitrary structured content models; choose Ghost when the content is articles, pages, and authors

Complementary

Mailchimp

Mailchimp can syndicate Ghost posts as newsletter campaigns

Pair Ghost (source of truth) with Mailchimp (newsletter delivery) when the team prefers Mailchimp over Ghost's built-in newsletter

FAQs

Specific to using Ghost Content API API through Jentic.

What authentication does the Ghost Content API use?

The Content API uses an apiKey scheme — the key is passed as a query parameter named 'key' on every request. Through Jentic the key is stored encrypted in the vault and the agent receives a scoped invocation capability, which avoids the key leaking into client-side request logs.

Can I retrieve a Ghost post by its slug?

Yes. GET /posts/slug/{slug}/ returns the post matching the slug, including title, content, tags, authors, and published_at. This is the canonical way to resolve a URL slug back to the post record without scanning the full list.

What are the rate limits for the Ghost Content API?

The spec does not declare specific rate limits. Self-hosted Ghost instances inherit limits from the deployment; Ghost(Pro) hosted publications apply per-account quotas. Production front-ends should cache responses (most posts change rarely) and implement backoff on 429 responses.

How do I list posts from a Ghost site through Jentic?

Search Jentic for 'list ghost posts'. Jentic returns the GET /posts/ operation with its query-parameter schema (filter, order, include); load it, set the filter you want, and execute. The response contains the post array along with pagination metadata.

Does the Ghost Content API allow creating or updating posts?

No. The Content API is read-only. Creating, updating, or deleting posts and pages requires the separate Ghost Admin API which uses a different authentication scheme and exposes write operations.

Can I read membership tiers from the Content API?

Yes. GET /tiers/ lists the membership tiers configured on the publication along with their pricing and benefit text, which is what front-ends use to render the subscription paywall component.