Export what a channel plays as CSV
This endpoint returns the same timeline as the get what a channel plays endpoint, as a CSV file you can open in a spreadsheet or hand to a scheduling team.
How it works
-
Make a GET request to this endpoint with the channel’s
typeand the period you want, usingstartTimeandendTime. Both are required. -
The response is a CSV file, sent as
text/csv; charset=utf-8with aContent-Dispositionheader naming itschedule_<channelId>_<type>_from_<start>_to_<end>.csv. The body has no byte-order mark and starts with the header rowMedia ID,Duration (seconds),Start Time,End Time,Type; a loop channel adds,Program ID. -
Each row is one thing the channel plays, in play order.
Duration (seconds)is whole seconds, rounded down;Start TimeandEnd Timekeep sub-second precision, so a value such as2026-09-02T18:00:52.208Zis normal.
Bumpers
On a schedule channel a bumper plays inside the event’s slot: the preroll runs from the event’s startTime for its own duration, the postroll ends at the event’s endTime, and the main media fills what is left between them. The CSV lists each bumper as a row of its own, with Type bumper and Media ID set to the id of the media that plays for the bumper, followed or preceded by the row for the main media with its shortened times. On a loop channel bumpers are already items of their own and appear the same way.
A single export can cover at most 10 days. A longer window is refused with a 422 naming endTime.
Example
A scheduling team exports next week’s running order for a channel and reviews it in a spreadsheet before the week starts.
Authentication
FastPix APIs are secured with Basic Authentication. Use your Access Token ID as the username and Secret Key as the password in the Authorization header of each API request.
- Username: Access Token ID
- Password: Secret Key
Activate your FastPix account to generate your API credentials. See the guide here
Path parameters
Query parameters
The start of the period to export, in yyyy-MM-dd'T'HH:mm:ss format and interpreted as UTC.
The end of the period to export, in yyyy-MM-dd'T'HH:mm:ss format and interpreted as UTC. It must be later than startTime.
Response headers
Marks the body as a download and carries the generated filename, schedule_<channelId>_<type>_from_<start>_to_<end>.csv, where the times are the requested startTime and endTime with : replaced by -.
Response
Channel timeline exported successfully. The body is the CSV file itself, with no byte-order mark, starting with the header row.