AI answers drawn only from these docs, with links to the pages used.

Event Stream API Overview

Last updated on October 09, 2026.

The Event Stream provides a REST API for creating and retrieving events on your Instance. This section covers the key concepts for working with the Event Stream API as a developer.

Authentication

All Event Stream API requests need your Instance API Key in the Authorization header, with no Bearer prefix. You can find this key in your Instance Admin under Integrations > Instance API Key. The instance uses its own Event Stream API Key to pass your request on, so you do not send that key.

Include the key in the Authorization header of every request:

Base Endpoint

The Event Stream API is available at:

This endpoint supports both POST (create events) and GET (retrieve events) methods.

Writing Events

Send a POST request to the events endpoint with a JSON body that contains at least a (text or HTML). The instance sets to the time it receives the request, and replaces any datetime you send.

Optional fields include , , , , , and .

For the complete field reference and example requests, see your Instance API documentation at <instance URL>/admin/api.

Reading Events

Send a GET request to the events endpoint with query parameters to filter and paginate results:

ParameterDescription
Page number for pagination
Number of events per page
Start of date range (epoch timestamp)
End of date range (epoch timestamp)
Search events by description (contains match)

Use Cases

  • Log external system events (e.g. payment received, email sent, webhook triggered)
  • Track user activity from your front-end application
  • Build custom dashboards by reading events from the API
  • Integrate with third-party systems that consume event data

Further Reading

Have a suggestion for this page?

Didn't quite find what you are looking for or have feedback on how we can make the content better then we would love to hear from you. Please provide us feedback and we will get back to you shortly.