Get Latest Publications
| Version | Change | 
|---|---|
| release-2021-06 | Added reverse,contentTypes,id.gte(and other range filters),publishedAt.gte(and other range filters) | 
| release-2024-03 | Added ignoreComponentConditionsandcomponentConditionsquery parameters. | 
| release-2023-09 | The type documentswithinreferenceschanged todocumentwhere every document id has a separate reference entry. | 
| release-2025-03 | Support for top-level property referencesin version2025-03 | 
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 4 possible top-level properties:
- systemdata
- metadata
- content
- references
Use Cases
- Bulk export of data, e.g. a specific Content Type
Endpoint
GET /api/2025-09/documents/latestPublicationsParameters
| Name | Type | Required | Notes | 
|---|---|---|---|
| ?fields | string | Filters which (comma separated) properties are included in the response. Defaults to systemdata,metadata,content,references | |
| ?reverse | boolean | Order publications in ascending order instead of the default descending order (the property used for sorting is lastPublicationDate). This is useful if you want to paginate using a time based filter | |
| ?homepage | boolean | Return only the document labeled as homepage in the current project | |
| ?contentTypes | string | Comma separated list of content types to use as filter | |
| ?documentTypes | string | Comma separated list of document types to use as filter. Can be one of  | |
| ?id.gte | string | Filter by document id range. Supported filters:  The id range filter is useful if you want to export a lot of documents. You can do many requests in parallel against the api, where you filter by the specific ranges. This query is much more flexible than an offset-based filter and works with millions of documents. Request 1:  | |
| ?id | string | Filter by one or multiple document ids. Example 1:  | |
| ?publishedAt.gte | string | Filter by publish date range. Supported filters:  Example: To retrieve all publications since a specific timestamp, use  | |
| ?ignoreComponentConditions | boolean | Added in: release-2024-03Provides a way to opt out of component filtering and return all content regardless of whether each component passes the conditional checks. Default:  | |
| ?componentConditions | string | Added in: release-2024-03JSON stringified object which contains the component conditions you would like to apply. Default:  | |
| ?limit | integer | A limit for how much published documents to retrieve. Defaults to 100. Max. 100 | |
| ?offset | integer | An offset into the query. Useful when getting more than 100 results (pagination). Max. 10000. Prefer range based filters like id.get or publishedAt.gte | 
Response
Get Latest Publications
With the introduction of the new versioning strategy, thev1andbetaversions are now available as2025-03version. If you use any of those versions, you can safely change your integration to the2025-03version, which now contains both functionalities without any other changes.
| Version | Change | 
|---|---|
| release-2023-09 | The type documentswithinreferenceschanged todocumentwhere every document id has a separate reference entry. | 
| release-2024-03 | Added ignoreComponentConditionsandcomponentConditionsquery parameters. | 
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 4 possible top-level properties:
- systemdata
- metadata
- content
- references
Use Cases
- Bulk export of data, e.g. a specific Content Type
Endpoint
GET /api/beta/documents/latestPublicationsParameters
| Name | Type | Required | Notes | 
|---|---|---|---|
| ?fields | string | Filters which (comma separated) properties are included in the response. Defaults to systemdata,metadata,content,references | |
| ?reverse | boolean | Order publications in ascending order instead of the default descending order (the property used for sorting is lastPublicationDate). This is useful if you want to paginate using a time based filter | |
| ?homepage | boolean | Return only the document labeled as homepage in the current project | |
| ?contentTypes | string | Comma separated list of content types to use as filter | |
| ?documentTypes | string | Comma separated list of document types to use as filter. Can be one of  | |
| ?id.gte | string | Filter by document id range. Supported filters:  The id range filter is useful if you want to export a lot of documents. You can do many requests in parallel against the api, where you filter by the specific ranges. This query is much more flexible than an offset-based filter and works with millions of documents. Request 1:  | |
| ?id | string | Filter by one or multiple document ids. Example 1:  | |
| ?publishedAt.gte | string | Filter by publish date range. Supported filters:  Example: To retrieve all publications since a specific timestamp, use  | |
| ?ignoreComponentConditions | boolean | Added in: release-2024-03Provides a way to opt out of component filtering and return all content regardless of whether each component passes the conditional checks. Default:  | |
| ?componentConditions | string | Added in: release-2024-03JSON stringified object which contains the component conditions you would like to apply. Default:  | |
| ?limit | integer | A limit for how much published documents to retrieve. Defaults to 100. Max. 100 | |
| ?offset | integer | An offset into the query. Useful when getting more than 100 results (pagination). Max. 10000. Prefer range based filters like id.get or publishedAt.gte | 
Response
Get Latest Publications
This endpoint has changes in version 2025-09.
| Version | Change | 
|---|---|
| release-2021-06 | Added reverse,contentTypes,id.gte(and other range filters),publishedAt.gte(and other range filters) | 
| release-2024-03 | Added ignoreComponentConditionsandcomponentConditionsquery parameters. | 
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 3 possible top-level properties:
- systemdata
- metadata
- content
Use Cases
- Bulk export of data, e.g. a specific Content Type
Endpoint
GET /api/v1/documents/latestPublicationsParameters
| Name | Type | Required | Notes | 
|---|---|---|---|
| ?fields | string | Filters which (comma separated) properties are included in the response. Defaults to systemdata,metadata,content | |
| ?reverse | boolean | Order publications in ascending order instead of the default descending order (the property used for sorting is lastPublicationDate). This is useful if you want to paginate using a time based filter | |
| ?homepage | boolean | Return only the document labeled as homepage in the current project | |
| ?contentTypes | string | Comma separated list of content types to use as filter | |
| ?documentTypes | string | Comma separated list of document types to use as filter. Can be one of  | |
| ?id.gte | string | Filter by document id range. Supported filters:  The id range filter is useful if you want to export a lot of documents. You can do many requests in parallel against the api, where you filter by the specific ranges. This query is much more flexible than an offset-based filter and works with millions of documents. Request 1:  | |
| ?id | string | Filter by one or multiple document ids. Example 1:  | |
| ?publishedAt.gte | string | Filter by publish date range. Supported filters:  Example: To retrieve all publications since a specific timestamp, use  | |
| ?ignoreComponentConditions | boolean | Added in: release-2024-03Provides a way to opt out of component filtering and return all content regardless of whether each component passes the conditional checks. Default:  | |
| ?componentConditions | string | Added in: release-2024-03JSON stringified object which contains the component conditions you would like to apply. Default:  | |
| ?limit | integer | A limit for how much published documents to retrieve. Defaults to 100. Max. 100 | |
| ?offset | integer | An offset into the query. Useful when getting more than 100 results (pagination). Max. 10000. Prefer range based filters like id.get or publishedAt.gte |