Skip to main content
POST
/
block
/
{slug}
/
{key}
curl -X POST 'https://fetch-<project-token>.frontic.com/block/<block-slug>/<record-key>' \
  -H 'fs-context: <context-key>'

{
  "name": "Aurora Snowboard",
  "price": {
    "amount": 49900,
    "currency": "eur",
    "precision": 2
  },
  "image": {
    "src": "https://cdn.demo-shop.com/products/aurora.jpg",
    "altText": "Aurora Snowboard front view"
  },
  "availability": "in-stock"
}

Documentation Index

Fetch the complete documentation index at: https://docs.frontic.com/llms.txt

Use this file to discover all available pages before exploring further.

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

​
project-token
string
required
Your project’s Fetch token, embedded in the subdomain.
​
slug
string
required
The block’s slug, e.g. <block-slug>. Per project — see your block’s detail view in the API Builder.
​
key
string
required
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 uses fs-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

CodeWhen
200Block found and rendered
401fs-secret missing or wrong (only when the project has fetch keys configured)
404No record matches the key, or the block slug doesn’t exist for the resolved context
403Project’s plan limit for Fetch API requests exceeded
{
  "name": "Aurora Snowboard",
  "price": {
    "amount": 49900,
    "currency": "eur",
    "precision": 2
  },
  "image": {
    "src": "https://cdn.demo-shop.com/products/aurora.jpg",
    "altText": "Aurora Snowboard front view"
  },
  "availability": "in-stock"
}

curl -X POST 'https://fetch-<project-token>.frontic.com/block/<block-slug>/<record-key>' \
  -H 'fs-context: <context-key>'