Get Latest Publication
| Version | Change |
|---|---|
| release-2024-03 | Added ignoreComponentConditions and componentConditions query parameters. |
| release-2025-09 | Support for the renditions query string got removed. An error is reported if used. |
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 5 possible top-level properties:
- systemdata
- metadata
- references
- content
Advantages
- Be able to cache the response, because it only changes on a republish (does not contain resolved refs)
- Useful for a pull architecture
- (deprecated) Supports the Render Pipeline with it’s Renditions
Related
Use Cases
- Load an unresolved Publication with the required information to render a document/page.
- Export the unresolved Publication to another system and get changes via Publication Events or Webhooks
Endpoint
GET /api/2025-09/documents/{documentId}/latestPublicationParameters
| Name | Type | Required | Notes |
|---|---|---|---|
| documentId | integer | x | |
| ?fields | string | Filters which (comma separated) properties are included in the response. Defaults to systemdata,references,metadata,content. | |
| ?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: |
Response
Get Latest Publication
| Version | Change |
|---|---|
| release-2024-03 | Added ignoreComponentConditions and componentConditions query parameters. |
| release-2025-09 | The renditions query string is deprecated and logs a warning when used |
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 5 possible top-level properties:
- systemdata
- metadata
- references
- content
- renditions
Advantages
- Be able to cache the response, because it only changes on a republish (does not contain resolved refs)
- Useful for a pull architecture
- (deprecated) Supports the Render Pipeline with it’s Renditions
Related
Use Cases
- Load an unresolved Publication with the required information to render a document/page.
- Export the unresolved Publication to another system and get changes via Publication Events or Webhooks
- (deprecated) Provides a Publication via a Rendition for a delivery in another format like
RSS,XML
Endpoint
GET /api/2025-09/documents/{documentId}/latestPublicationParameters
| Name | Type | Required | Notes |
|---|---|---|---|
| documentId | integer | x | |
| ?fields | string | Filters which (comma separated) properties are included in the response. Defaults to systemdata,metadata,content,references. | |
| ?renditions | string | A comma-separated list of rendition handles. Example: | |
| ?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: |
Response
Get Latest Publication
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-2024-03 | Added ignoreComponentConditions and componentConditions query parameters. |
| release-2023-09 | The type documents within references changed to document where every document id has a separate reference entry. |
| release-2025-09 | The renditions query string is deprecated and logs a warning when used |
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 5 possible top-level properties:
- systemdata
- metadata
- references
- content
- renditions
Advantages
- Be able to cache the response, because it only changes on a republish (does not contain resolved refs)
- Useful for a pull architecture
- (deprecated) Supports the Render Pipeline with it’s Renditions
Use Cases
- Load an unresolved Publication with the required information to render a document/page.
- Export the unresolved Publication to another system and get changes via Publication Events or Webhooks
- (deprecated) Provides a Publication via a Rendition for a delivery in another format like
RSS,XML
Endpoint
GET /api/beta/documents/{documentId}/latestPublicationParameters
| Name | Type | Required | Notes |
|---|---|---|---|
| documentId | integer | x | |
| ?fields | string | Filters which (comma separated) properties are included in the response. Defaults to systemdata,metadata,content,references. | |
| ?renditions | string | A comma-separated list of rendition handles. Example: | |
| ?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: |
Response
Get Latest Publication
This endpoint has changes in version 2025-09.
| Version | Change |
|---|---|
| release-2024-03 | Added ignoreComponentConditions and componentConditions query parameters. |
| release-2025-09 | The renditions query string is deprecated and logs a warning when used |
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 4 possible top-level properties:
- systemdata
- metadata
- content
- renditions
Advantages
- Be able to cache the response, because it only changes on a republish (does not contain resolved refs)
- Useful for a pull architecture
- (deprecated) Supports the Render Pipeline with it’s Renditions
Related
Use Cases
- Load an unresolved Publication with the required information to render a document/page.
- Export the unresolved Publication to another system and get changes via Publication Events or Webhooks
- (deprecated) Provides a Publication via a Rendition for a delivery in another format like
RSS,XML
Endpoint
GET /api/v1/documents/{documentId}/latestPublicationParameters
| Name | Type | Required | Notes |
|---|---|---|---|
| documentId | integer | x | |
| ?fields | string | Filters which (comma separated) properties are included in the response. Defaults to systemdata,metadata,content. | |
| ?renditions | string | A comma-separated list of rendition handles. Example: | |
| ?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: |