Quickstart

Point an existing Storyblok project at Exacta in three steps, without changing a line of component code.

1. Connect your space

In the Exacta dashboard, add your Storyblok space id and a management token. Exacta uses the management token to read your content structure and to mint the delivery tokens it needs — it never writes to your space.

Once connected, run a sync. This pulls every story and folder into the preview branch, in both their published and draft states, and creates the default branches.

2. Create a delivery token

Open the Tokens page and create a token on the branch you want to read. Tokens are scoped to exactly one branch, which is what makes an environment a configuration change rather than a code change.

  • public — published content only. Safe to ship in a frontend bundle.
  • preview — also exposes drafts, and only on the preview branch. Keep it server-side.

3. Point your client at Exacta

Every official Storyblok client accepts a custom endpoint. Change it, and nothing else in your code has to move.

javascript
import { storyblokInit, apiPlugin } from '@storyblok/js'

storyblokInit({
  accessToken: process.env.EXACTA_TOKEN,
  use: [apiPlugin],
  apiOptions: {
    // The only line that changes.
    endpoint: 'https://api.exacta.im/v2/cdn',
  },
})

Or call it directly, with no client at all:

shell
curl "https://api.exacta.im/v2/cdn/stories?token=$EXACTA_TOKEN&per_page=5"

4. Promote when you are ready

Editors keep working in Storyblok. When you want those changes on staging or production, sync the preview branch and then promote. Only published content moves; drafts stay in preview by construction, not by convention.