Generate or retrieve a timelapse
List a project's rendered media, and request a new timelapse without tripping over the required fields.
A timelapse compresses weeks of a site into seconds. Unlike a snapshot it is rendered asynchronously: you request one, the platform processes it, and it appears in the project's media hub when ready.
Retrieve what already exists
Timelapses, clips and compares a project has produced.
curl -H "Authorization: Bearer $EVERCAM_TOKEN" \
"https://media.evercam.io/v2/projects/$PROJECT_EXID/media-hub"Items carry a title, a type and — once processing finishes — a file URL you
can put straight into a video element.
Not every item is playable yet
A queued or processing item has no file URL. Check for one before rendering, and show a "still processing" state otherwise.
Request a new timelapse
Queues a timelapse for rendering.
All seven fields are required
camera_exid, title, duration, from_datetime, to_datetime,
schedule and video_options are all mandatory. The last two are easy to
miss because they are objects rather than plain values — omitting them fails
the request rather than falling back to a default.
curl -X POST "https://media.evercam.io/v2/projects/$PROJECT_EXID/media-hub/timelapses" \
-H "Authorization: Bearer $EVERCAM_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"camera_exid": "dorset-street-i",
"title": "Foundation pour",
"duration": 30,
"from_datetime": "2026-07-01T08:00:00.000+00:00",
"to_datetime": "2026-07-31T18:00:00.000+00:00",
"schedule": {},
"video_options": {}
}'duration is the length of the finished video in seconds — not the period it
covers, which is set by from_datetime and to_datetime. Both datetimes use
the same ISO 8601 form as the
timeline endpoints.
Rendering is not instant. Poll the media hub until the new item has a file URL.
Try it
The demo below lists and plays your project's real media. Creation is not wired to a button, because rendering is a long-running write against your own account — use the request above to queue one.