Overview
Retrieve detailed highlight package records for account-level dashboard sync. Unlike the lightweight list endpoint, this response includes package metadata,otio_timeline EDLs, and rendered edit URLs when available.
Use this endpoint when you need many full package records in one request. For example, a dashboard can fetch the first 50 packages for an account instead of calling GET /highlight-packages/{id} for each package.
The endpoint supports ETag and If-None-Match. Store the ETag from a 200 response and send it on the next poll; the API returns 304 Not Modified when package status, EDL, rendered edit state, and metadata for that exact account/filter/page have not changed.
The
ETag includes the stable rendered asset state, such as whether a render exists and the stored rendered edit URL. It does not change just because the API regenerates an expiring signed URL.Request
Query Parameters
Response
Polling with ETags
On a200 response, save both the response body and the ETag header:
304, keep using the package data from your cached 200 response. The API sends 304 only when the page’s package data is unchanged, including statuses, EDLs, rendered edit state, selected highlights, and metadata.

