Exports are the tracked print component of content items. This allows the system to maintain completely separate states for print and web workflows and content, while maintaining a link between the two.

GET /v3/export/{uuid}

Get export for content item with given UUID.

Acl Action: EXPORT get

Example Response: See GET /v3/content/{uuid}

GET /v3/export/{uuid}/as/{type}

Return an export as a specific type. Currently supports:

  • icml - ICML data suitable for Adobe applications.
  • html - HTML file.
  • text - Plain text.

Acl Action: EXPORT dump

Example Response:

Text content

PUT /v3/export/{uuid}

Update export for given content uuid. Providing content will also generate a new version.

Acl Action: EXPORT update

Example Request:

{
    'workflow_id': 1
    'assignee_id': 1
    'issue_id': 1
    'workflow_section_id': 1
    'assignee_id': 1
    'content': 'some content'
}

Example Response: See GET /v3/content/{uuid}

PUT /v3/export/push/{uuid}

Push an export from print to web. This will replace the web content with the print export's content.

Acl Action: EXPORT push

Example Response: See GET /v3/content/{uuid}

PUT /v3/export/pull/{uuid}

Pull web content into the export. This will replace the print export's content with the web item.

Acl Action: EXPORT pull

Example Response: See GET /v3/content/{uuid}

PUT /v3/export/lock/{uuid}

Create a lock notification for a content item.

Note this is only a notification and DOES NOT control access to the item.

Acl Action: EXPORT lock

Example Response: See GET /v3/content/{uuid}

DELETE /v3/export/lock/{uuid}

Remove lock. Again, locks for exports are notifications, not hard locks.

Acl Action: EXPORT lock

Example Response: See GET /v3/content/{uuid}