The flow replayed with sample data. Use ↻ to play it again.
Fetch structured fields, articles, translations and search into any front-end. The API is read-only and ETag-cached.
The read-only design means public content can be exposed safely to the outside world. Write paths stay inside the CMS workflow, so there is no risk of content being changed through the API.
ETag caching avoids re-fetching unchanged responses, keeping delivery fast. It exposes the structured content model and localization directly, so any front-end can fetch per-market content.
- Fetch structured fields, articles, translations and search
- A read-only public API with no write access
- Per-market, per-locale values as-is
- ETag caching for fast responses
How it works
- 1From your front-end, fetch published page fields by market and page key.
- 2Fetch translations per market and locale from the translations endpoint.
- 3Fetch the articles attached to a page from the page-articles endpoint.
- 4Set a revalidation interval on the front-end that works with ETag caching.
FAQ
Can content be changed through the API?
No. The API is read-only; changes only happen through the CMS review and publish workflow.
Why doesn't a published change appear right away?
The public API is cached, so allow revalidation to complete.
Which markets can we fetch?
Currently Vietnam (vn), the Philippines (ph) and Indonesia (id).