Skip to main content

Response structure

All successful API responses return JSON with a data property containing the requested content. List endpoints also include a meta property with pagination information. Detail endpoints for single items return only the data property. List response:
Detail 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:
Page Type List:

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:
Single Post Detail:

Reference field responses

Reference fields return different data based on the levels parameter:

Level 1 (URIs only)

Level 2+ (complete objects)

Media field formats

Media fields can return data in two formats based on the alt_media_text parameter:

Default format (URL string)

When alt_media_text=0 (default):

Object format with alt text

When alt_media_text=1:

Localized responses

When requesting content in a specific locale using the locale 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)

Write operations are processed asynchronously. The 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

Use page and page_size parameters:
Response includes:

Offset-based pagination

Use limit and offset parameters:
Response includes:

Content-type headers

Request headers

Response headers

Next steps

HTTP Status Codes

Understand error responses

Rate Limits

Learn about API limits

REST Endpoints

View all available endpoints