True SSR in Next.js including headless rendering

The Spectare SSR path for Next.js has two layers: a server-side data fetch and a conditional render that switches between true SSR and a client fallback when the signal is weak. In a Next.js server component, call POST /api/assemble/ssr with your org API key and render the returned assembly. The personalised HTML ships in the initial response with zero flicker.

The response is structured JSON throughout, never HTML. Every slot is a plain string, number, image URL, or link object, so you can pass the result to your own components rather than using ComponentRenderer if you prefer. The component name on each part is a semantic hint, not a rendering instruction. This headless path is documented in the API reference under Headless rendering.

If you would rather skip the component vocabulary entirely, add a format field set to flat in the request body. The response comes back as plain page furniture: one hero, an ordered sections array with each entry carrying a kind field, one cta, and an optional announcement. The content is identical to the default shape and the two formats share the same cache cells, so you pay no performance penalty for choosing flat.

Conversion attribution works the same way on either shape. Each part in the flat response carries an atomIds array. Pass those ids in your conversion POST and Spectare credits the atoms that were actually rendered, end to end.