Use your content anywhere. Keep the visual editor for your team.

Fetch published pages and content from MarketingEngine over REST or GraphQL while your marketers keep editing visually.

What you get

REST API

Published pages, entries, content models, and locales as JSON, under /api/v1/delivery/v1. Authenticate with a site-scoped key in the X-MarketingEngine-Api-Key header.

GraphQL API

Query content models, entries, fields, locales, references, and page structures from a single endpoint at /api/v1/delivery/v1/graphql.

API keys

Each key belongs to one site, is stored hashed, and is rate limited so one site cannot use up another site's allowance.

Search and languages

Query published search entries and fetch content in any language you have set up, so your app can offer fast search and localized pages.

How to call it

Create a key once and keep it on your server. Fetch published pages from REST or GraphQL server-side, and handle three cases explicitly: 401 (key missing or revoked), 404 (page unpublished or slug not found), and 429 (rate limit reached). Never expose the key in browser JavaScript.

Developer questions

Do I have to use the MarketingEngine renderer?

No. Use the hosted renderer, the REST API, the GraphQL API, or a mix, depending on the surface.

How are API keys protected?

Keys are stored hash-only and can only read published content. They cannot be used to edit your site.