A sandbox to build against

Embed
Preview of the card
<a href="https://forumulate.com/reference/sandbox"><img src="https://forumulate.com/reference/_api/public/orgs/046a9bc0-d530-43ae-9bae-af7945008cda/spaces/8042f004-e3d9-445f-b7a4-b6c1f86836e6/pages/ff6802e1-729a-4cf0-8bbf-5d2e58f194aa/social-card.svg?v=3e7ae33eec8b" alt="A sandbox to build against" width="600" height="315"></a>

Build and test against real shapes before you ask anybody for a credential.

The token

Organization: 4766b8a4-57da-48f0-91ff-c46da0f8d205
Token:        cft_3eA-ii9rVu67oEkfOhoEgzRd_YauvCojYBB28FSPMFM

It is read-only and scoped to the sandbox's spaces — it cannot write, and it cannot see any other organization or space. That is the same token scoping you can use for your own integrations: ask for spaceIds when you mint one, and an integration that syncs one public space stops holding a credential that can read a private one.

What is in it

curl -H "Authorization: Bearer cft_3eA-ii9rVu67oEkfOhoEgzRd_YauvCojYBB28FSPMFM" \
  https://forumulate.com/api/orgs/4766b8a4-57da-48f0-91ff-c46da0f8d205/spaces

  • Runbooks — a DOCS space whose pieces have real named slots (summary, before, steps, learned), so a mapper that turns slots into headings has something honest to work against.

  • Community — a forum space, so you can see a topic-backed piece answer the same way a page does.

A whole space in four requests

curl -H "Authorization: Bearer cft_3eA-ii9rVu67oEkfOhoEgzRd_YauvCojYBB28FSPMFM" \
  -H "Forumulate-Version: 2026-09-01" \
  "https://forumulate.com/api/orgs/4766b8a4-57da-48f0-91ff-c46da0f8d205/spaces/<spaceId>/items?include=sections&limit=50"

Then keep sync.checkpoint and ask again with updated_since — see Incremental sync.

The content here is stable and rewritten only when we change the shapes it demonstrates. If you need something in it that is missing, ask in the community.

The Forumulate teamUpdated