Returns a list of real-time servers that can be used for long-polling updates to the event stream.
Long polling is the concept where a HTTP request is kept open until the server sends a response, then repeating the process over and over to receive updated responses.
Long polling the event stream can only be used for user events, not for enterprise events.
To use long polling, first use this endpoint to retrieve a list of long poll URLs. Next, make a long poll request to any of the provided URLs.
When an event occurs in monitored account a response with the value
new_change
will be sent. The response contains no other details as
it only serves as a prompt to take further action such as sending a
request to the events endpoint with the last known
stream_position
.
After the server sends this response it closes the connection. You must now repeat the long poll process to begin listening for events again.
If no events occur for a while and the connection times out you will
receive a response with the value reconnect
. When you receive this response
you’ll make another call to this endpoint to restart the process.
If you receive no events in retry_timeout
seconds then you will need to
make another request to the real-time server (one of the URLs in the response
for this endpoint). This might be necessary due to network errors.
Finally, if you receive a max_retries
error when making a request to the
real-time server, you should start over by making a call to this endpoint
first.
This operation is performed by calling function GetEventsWithLongPolling
.
See the endpoint docs at API Reference.
await client.Events.GetEventsWithLongPollingAsync();
- headers
GetEventsWithLongPollingHeaders
- Headers of getEventsWithLongPolling method
- cancellationToken
System.Threading.CancellationToken?
- Token used for request cancellation.
This function returns a value of type RealtimeServers
.
Returns a paginated array of servers that can be used instead of the regular endpoints for long-polling events.
Returns up to a year of past events for a given user or for the entire enterprise.
By default this returns events for the authenticated user. To retrieve events
for the entire enterprise, set the stream_type
to admin_logs_streaming
for live monitoring of new events, or admin_logs
for querying across
historical events. The user making the API call will
need to have admin privileges, and the application will need to have the
scope manage enterprise properties
checked.
This operation is performed by calling function GetEvents
.
See the endpoint docs at API Reference.
await client.Events.GetEventsAsync(queryParams: new GetEventsQueryParams() { StreamType = GetEventsQueryParamsStreamTypeField.AdminLogs, Limit = 1, CreatedAfter = createdAfterDate, CreatedBefore = createdBeforeDate });
- queryParams
GetEventsQueryParams
- Query parameters of getEvents method
- headers
GetEventsHeaders
- Headers of getEvents method
- cancellationToken
System.Threading.CancellationToken?
- Token used for request cancellation.
This function returns a value of type Events
.
Returns a list of event objects.
Events objects are returned in pages, with each page (chunk)
including a list of event objects. The response includes a
chunk_size
parameter indicating how many events were returned in this
chunk, as well as the next stream_position
that can be
queried.