Get Latest Publication
Required scope:
public-api:read
Description
The endpoint provides an unresolved Publication with 5 possible top-level properties:
- systemdata
- metadata
- content
- renditions
- references
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
Related
Endpoint
GET api/beta/documents/:documentId/latestPublication
Parameters
Name | Type | Required | Notes |
---|---|---|---|
:documentId | integer | x | |
?fields | string | Filters which (comma separated) properties are included in the response. Defaults to ‘systemdata,metadata,content’ (no renditions). | |
?renditions | string | A comma-separated list of rendition handles. Example: ?renditions=web,json | |
?ignoreComponentConditions | boolean | Provides a way to opt out of component filtering and return all content regardless of whether each component passes the conditional checks. Added in: release-2024-03 Default: false | |
?componentConditions | string | JSON stringified object which contains the component conditions you would like to apply. Added in: release-2024-03 Default: dateTime: new Date() Example: ?componentConditions={"dateTime":"2024-02-14T17:25:10.391Z"} |