Fetch API
Fetch a Block
POST
Fetch a single block (Detail Block) by its key. Each block in your project has its own slug — defined when the block is created in the API Builder — and a single record key identifies which record to render.
The endpoint accepts both
POST and GET (no body in either case); POST is canonical and what the Client SDK uses. The block payload is shaped by your block’s field configuration: every field becomes a property on the response, with composite shapes preserved (Price, Media, etc.). Translatable fields resolve to the active locale; scoped fields resolve to the active scope.
Path Parameters
Your project’s Fetch token, embedded in the subdomain.
The block’s slug, e.g.
<block-slug>. Per project — see your block’s detail view in the API Builder.The record key to fetch. The block’s connected Data Storage determines which key field is used.
Headers
See Headers on the overview for the full set. The block endpoint usesfs-context, fs-domain, fs-version, and fs-secret (only when the project has fetch keys configured).
Response
Project-specific. Generate the Client SDK for typed access, or read the live shape from the project’s OpenAPI spec.Status codes
| Code | When |
|---|---|
200 | Block found and rendered |
401 | fs-secret missing or wrong (only when the project has fetch keys configured) |
404 | No record matches the key, or the block slug doesn’t exist for the resolved context |
403 | Project’s plan limit for Fetch API requests exceeded |