The Datahose - Read Events endpoint returns the Real Time Events happening in the pod, either since the time the datahose feed was created or since the previous feed was read by the bot. The
ackId has an essential role in retrieving the right events for the bot.
The ackId should indeed be null or empty for the first call. Then, for subsequent requests, the ackId from the previous payload should be reused to confirm the reading of previous events already retrieved by the bot.
Please note that you can very easily access this API via our BDKs in Java and Python.
If a batch of messages is not confirmed by sending the
ackId, the messages that are there will be returned in the subsequent readings and may blend into the newer messages.
The service account user needs to have both the Can read from datahose feeds and Can create datahose feeds entitlements enabled to call this endpoint.