Response structure
All successful API responses return JSON with adata property containing the requested content. List endpoints also include a meta property with pagination information. Detail endpoints for single items typically return only the data property. The single Blog Post detail endpoint is an exception and also returns a meta object with next/previous post navigation (see Blog Posts response below).
List response:
The meta object
Included in list responses and blog post detail responses. Contains metadata about the response such as pagination information or navigation links:
For offset-based pagination:
The data object
Contains the actual content. Structure varies by endpoint type:
- List endpoints: Array of items or keyed object
- Detail endpoints: Single item object
- Write operations: Success confirmation or created item
Content type responses
Pages response
Single Page Detail:Collections response
Collection List:Collection items include a nested
meta object with the item’s numeric id, which is required for update and delete operations.Blog Posts response
Post List:Reference field responses
Reference fields return different data based on thelevels parameter:
Level 1 (URIs only)
Level 2+ (complete objects)
Media field formats
Media fields can return data in two formats based on thealt_media_text parameter:
Default format (URL string)
Whenalt_media_text=0 (default):
Object format with alt text
Whenalt_media_text=1:
Localized responses
When requesting content in a specific locale using thelocale query parameter (e.g., ?locale=de), the response returns the localized content for that locale. The response structure is the same as a standard response — there is no additional locale field in the response body:
Request formats
GET requests
Query parameters are passed in the URL:POST/PUT/PATCH requests
Data is sent as JSON in the request body:Write operation responses
Successful creation (202 Accepted)
pending status indicates the request has been accepted and is being processed in the background.
Successful update (202 Accepted)
Successful deletion (204 No Content)
No response body is returned for successful deletions.Pagination patterns
Page-based pagination
Usepage and page_size parameters:
Offset-based pagination
Pages and Blog Posts list endpoints also acceptlimit and offset (Collections only support page and page_size):
Content-type headers
Request headers
Content-Type only applies to POST/PUT/PATCH requests that send a JSON body; GET requests don’t need it.
Response headers
Surrogate-Key and Surrogate-Control are Fastly cache-control headers used for purge-based invalidation; X-Robots-Tag keeps API responses out of search engine indexes.
Next steps
HTTP Status Codes
Understand error responses
Rate Limits
Learn about API limits
REST Endpoints
View all available endpoints