Introduction

Exacta gives a Storyblok space the branches that Storyblok itself puts behind the Pipelines add-on: a preview branch that mirrors your space, and staging and production branches that only ever receive content you have explicitly promoted.

It is delivered as a drop-in replacement for Storyblok’s Content Delivery API. Your components, your queries and your Storyblok client stay exactly as they are — you change the base URL and the token.

- https://api.storyblok.com/v2/cdn/stories?token=<storyblok-token>
+ https://api.exacta.im/v2/cdn/stories?token=<exacta-token>

How it works

Content is authored in Storyblok exactly as before — Exacta never asks anyone to change where they write. A sync pulls your space into the preview branch, and promotion copies published content forward from there.

• Preview mirrors your Storyblok space, including drafts. It is the only branch that ingests content.
• Staging and Production are frozen. They change only when you promote, and they receive published content only.
• Each branch has its own delivery tokens. The token selects the branch, so an environment is chosen by configuration rather than by code.

What this documentation covers

The Content Delivery API section is the contract your frontend depends on, and mirrors Storyblok’s field for field. The Branches section covers sync and promotion, which have no Storyblok equivalent on plans without Pipelines.

If you are moving an existing project across, start with the quickstart, then read migrating from Storyblok for the differences that matter.