Ghost Content API
Official vendor OpenAPI document · agent-readyMarketingContent 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.
Use for: I need to list the latest 10 posts from a Ghost site, Retrieve the post with slug 'product-launch-2026', Get the author profile for slug 'jane-doe', List all tags used on this Ghost publication
Not supported: Does not handle creating, updating, or deleting content, member subscriptions, or admin operations - use for Ghost read-only content delivery only.
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.
Install Jentic One Beta
Connect the Ghost Content API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ghost Content API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fghost.org%2Fghost" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fghost.org%2Fghost" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Ghost Content 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
List and look up tags used on posts and pages
Read membership tiers configured on the publication
Retrieve site settings (title, description, navigation) for header rendering
Use Cases
Patterns agents use Ghost Content 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
GET
/tags/slug/{slug}/
Retrieve a tag by slug
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Ghost Content API by hand means creating a Custom Integration key, appending it to the query string of every request against your own Ghost domain, and keeping that key out of your logs yourself. Through Jentic you install once, import the Ghost Content API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Ghost Content is read-only and puts the post id and slug in the URL path (/posts/{id}/, /posts/slug/{slug}/), so a rule can pin your agent to reading one post or its slug. You choose the operations it may call, and the Content API exposes no create, update, or delete actions to include.
Credential isolation
Your Ghost Content API key is stored once, encrypted, by your own Jentic One instance and injected at execution time, which matters because it rides in the query string. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Ghost posts' or 'get a Ghost post by slug', and Jentic returns the matching operation with its query-parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Ghost Content 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.
Can I limit what my agent is allowed to do with the Ghost Content API?
Yes. Because Jentic One is self-hosted, your own rules decide which operations your agent may call, and the Ghost Content API is read-only, so there are no create, update, or delete actions to expose in the first place. You can pin the agent to specific read operations such as GET /posts/, GET /posts/slug/{slug}/, GET /tags/, or GET /tiers/, since the post id and slug live in the URL path. The Content API key is stored once by your own instance and injected only when an allowed operation runs, so it never reaches the agent's prompt or logs.
GET STARTED