Ceros Developer Docs
Build on the Ceros platform. This site holds our developer guides and the Ceros API reference.
Start here
- Getting started: get an API key, make your first authenticated request, and learn how versioning works.
- API Reference: open API Reference in the top navigation to browse the endpoints. Each release has its own version selector.
- Embedding a Flex experience: choose a delivery mode and get the experience onto your own page.
What's here
Guides
How-to guides live in the Guides section of the sidebar. This area grows over time; today it covers getting started and versioning.
API Reference
Work with your Ceros content programmatically (experiences, folders, pages, and more) over a straightforward, API-key-authenticated REST API.
Every endpoint is versioned. Use the version selector to view a specific release, and see API versioning for how versions work and how to pin one.
Embedding
Embedding covers the four ways to put a published Flex experience in front of people: the Ceros-hosted standalone URL, an iframe embed, Flex Inline (iframeless, no server work), and Flex SSR (your server renders the experience into its own HTML, for SEO and fastest first paint).
Flex Experience SDK
The Flex Experience SDK lets you add your own JavaScript to a published Flex experience. Name the components you designed in Flex, then find them from a script and drive them — play a video, swap headline copy, toggle a state, navigate pages, or respond to a click.
Plugins
Plugins are integrations that connect Ceros to other platforms. Today this covers the Ceros AEM Connector for Adobe Experience Manager and the Ceros WordPress Plugin for WordPress posts and pages.