2

Event Hash and ID

We've been looking at pulling Events via the API. Here is a sample response from our system. We noticed there is an ID and a Hash. I don't see any documentation on what those represent. Can you help me understand what they are and what their impacts are?

The downstream consumer is interested to know:

  • Are they unique across the entire events database?
  • would they change if we backfill (assuming the recalculated event has the same start/end time/everything).
  • Anything else I'm not thinking to ask.
{
    "statusCode": "Good",
    "errors": [],
    "events": [
        {
            "StartsAt": "2026-01-16T08:57:00.7210000-06:00",
            "EndsAt": "2026-01-16T09:00:00.8570000-06:00",
            "AssetBasePath": "Flares.KAR.DREES_CF_TKFL",
            "AssociatedTags": [],
            "BelowMinDuration": false,
            "Duration": "00:03:00.1360000",
            "EndTriggerOffset": "00:00:00",
            "EventTypeName": "Flare Pilot Unlit",
            "Hash": "2763cd46-f663-467b-a5f2-980e63c5dbac",
            "Id": 678258,
            "Notify": "",
            "Properties": [],
            "StartTriggerOffset": "00:00:00"
        },
        {
            "StartsAt": "2026-01-16T06:59:01.7150000-06:00",
            "EndsAt": "2026-01-16T07:25:01.9360000-06:00",
            "AssetBasePath": "Flares.KAR.LATKA_CF_TKFL",
            "AssociatedTags": [],
            "BelowMinDuration": false,
            "Duration": "00:26:00.2210000",
            "EndTriggerOffset": "00:00:00",
            "EventTypeName": "Flare Pilot Unlit",
            "Hash": "cc394a91-98b7-415e-9437-3cd226c2eaab",
            "Id": 678203,
            "Notify": "",
            "Properties": [],
            "StartTriggerOffset": "00:00:00"
        },
        {
            "StartsAt": "2026-01-16T06:35:21.1190000-06:00",
            "EndsAt": "2026-01-16T06:36:01.1690000-06:00",
            "AssetBasePath": "Flares.TIL.JAMBERSW_CF_TKFL",
            "AssociatedTags": [],
            "BelowMinDuration": false,
            "Duration": "00:00:40.0500000",
            "EndTriggerOffset": "00:00:00",
            "EventTypeName": "Flare Pilot Unlit",
            "Hash": "dd4fc288-4ee7-488e-885c-3c8a109be7c5",
            "Id": 678184,
            "Notify": "",
            "Properties": [],
            "StartTriggerOffset": "00:00:00"
        }
    ],
    "continuation": "8DKotvtU3kgoWQoAAAAAAA=="
}

3 replies

null
    • smason
    • 11 hrs ago
    • Reported - view

    Hi ,

    Hash and ID are unique within the database and will change if the events are re-backfilled. They're mainly used for internal purposes, but you can search for a specific hash within the getEvents call. 

      • Real-Time Manager at CSE ICON
      • damon_vinciguerra.1
      • 11 hrs ago
      • Reported - view

       that’s helpful! Out of curiosity, why have 2 unique identifiers?

      • smason
      • 9 hrs ago
      • Reported - view

       

      ID was introduced in 25.4 with the new Calcs & Events functionality which you can display within the Events Table in Axiom and in a Trend Graph when when you're displaying events. It's a little more friendlier than a hash. I think we had to keep the hash for backwards compatibility if people used to look up a specific event using the read api.

Content aside

print this pagePrint this page
  • 2 Likes
  • 9 hrs agoLast active
  • 3Replies
  • 18Views
  • 4 Following