Fetch content
Make and verify a REST request for exact Published content.
Use server-side code and a key with delivery.readPublished scoped to the intended Backend and Environment. The article model key below is illustrative; replace it with a Data Type key from your Backend.
Creating a key requires apiKey.create. Listing key metadata and policy requires apiKey.read. The runtime key does not also require backend.read.
curl 'https://delivery.example.com/rest/article?first=1' \
-H 'x-api-key: YOUR_DELIVERY_KEY' \
-H 'x-backend-id: BACKEND_ID' \
-H 'x-environment-id: ENVIRONMENT_ID'{
"items": [{ "_id": "018f-example", "title": "Hello Jetrepo" }],
"total_count": 1,
"page_info": {
"has_next_page": false,
"has_previous_page": false,
"start_cursor": "CURSOR",
"end_cursor": "CURSOR"
}
}The response headers identify the exact Published manifest. Missing or invalid keys return 401; unresolved or disallowed Backend scope returns 403. Delivery-key resolution may be cached for up to the configured DELIVERY_AUTH_CACHE_TTL (5000 milliseconds by default). See credential timing before relying on revocation.
Use the per-Backend OpenAPI document at /openapi.json or the Scalar browser at /docs to discover resource fields and supported query parameters. OpenAPI is the machine-readable application contract; Jetrepo does not generate a client SDK.