Headless CMS: send pages to your own endpoint

The Headless CMS connector POSTs an approved Framesite page to a REST endpoint you own, as a JSON document your endpoint maps into your own schema. It fits Sanity, Contentful, Strapi, or a custom service. It does not update in place: each publish is a new POST.

What you need

A REST endpoint that accepts a JSON document and maps it into your schema, and an optional auth token if your endpoint requires one. You build the endpoint on your side, whether that is a serverless function, a webhook route, or an API in front of Sanity, Contentful, Strapi, or a custom store. Connecting requires a workspace admin.

Connecting your headless CMS

1. Open the Headless CMS card

   In Framesite, open Settings, then Destinations & connections, and find the Headless CMS card. Connecting destinations is limited to workspace admins.

2. Enter your endpoint

   Provide the REST endpoint URL and, if your endpoint requires it, an auth token. The token is sent as a Bearer header on each request.

   In Framesite

   1. Settings
   2. Destinations & connections
   3. Headless CMS

   

3. Send a test publish

   There is no live connection test. Save the connection, then publish a page and confirm your endpoint received and mapped the JSON document. The token is stored encrypted in our vault and never shown back.

What it does

Each time you publish an approved page, Framesite POSTs a JSON document to your endpoint. The document carries the page metadata, its URL, an excerpt, an image, the rendered HTML, and the structured data. Your endpoint maps that into your schema. Framesite does not update in place; every publish is a new POST, so your endpoint receives a fresh document each time.

Troubleshooting

• Nothing arrived, but there was no error.There is no live probe, so confirm the endpoint URL is correct and reachable, then send a test publish and watch your endpoint's logs.
• Your endpoint returns unauthorized. The token is sent as a Bearer header. Check that your endpoint expects that header and that the token is current.
• Duplicates are piling up. Each publish is a new POST with no dedupe. Handle idempotency in your endpoint if you need to collapse repeats.

Removing the connection

Open the Headless CMS card and click Disconnect. This removes the stored token from our systems immediately and ends all further requests to your endpoint. Anything your endpoint already stored is on your side and untouched. Reconnecting later starts from a fresh endpoint and token.