For the complete documentation index, see llms.txt. This page is also available as Markdown.

Event History

An Event history feed contains Event data and all published Elements which have completed.

Files

<static host>/events/<first two chars of event UUID>/<event UUID>/history.json
Assuming uuid of c83756ea-8247-40bb-8f32-64400bcbea93 and static host of https://example.com
https://example.com/events/c8/c83756ea-8247-40bb-8f32-64400bcbea93/history.json

Data

  • config contains an event data (object)

    • id event UUID(string)

    • name event name (string)

    • start_at start time as unix timestamp (integer)

    • start_at_iso start time in an ISO 8601 format (string)

    • end_at end time as unix timestamp (integer)

    • end_at_iso end time in an ISO 8601 format (string)

    • started started or already finished (boolean)

    • image_url URL to the image set in event settings (string)

    • custom_fields contains event level custom settings (object)

    • extra_time extra time of event

    • on_demand_time on demand of event

    • duration real event duration

    • original_duration original event duration

  • timeline contains objects with element data (array)

    • id element id (integer)

    • type name of a core element which this custom element built on top

    • content_type element content type (string)

    • duration element duration

    • published_at publish time as unix timestamp (integer)

    • published_at_iso publish time in an ISO 8601 format (string)

    • updated_at last time updated as unix timestamp (integer)

    • updated_at_iso last time updated in an ISO 8601 format (string)

    • duration duration in seconds (integer)

    • rating element's rating, when rating mode is enabled (float, precision depends on rating mode settings).

    • fixed is element has fixed duration (integer)

    • data processed data from enmasse

    • custom_fields contains element custom field values (object)

  • version file format version, currently 1 (integer)

custom_fields at event and element level contains field values as key-value object, where key is an custom field key from application spec.

Example

Last updated