Developers
Events2

Retrieve an event

GET/events/{event_id}

Retrieves a public event by its public ID.

Malformed IDs, internal event types, and events that are not accessible with the current credentials all return 404 Not Found.

Authorization

AuthorizationBearer <token>

Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.

In: header

Path Parameters

event_id*string

Public ID of the event, prefixed with evt_.

Header Parameters

X-Client-Request-Id?string

Optional client-generated identifier of the request, up to 64 characters from [A-Za-z0-9._-]. Echoed back in the response and recorded in the request log; it never replaces the server-generated X-Request-Id.

Lengthlength <= 64

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/events/string"
{  "data": {    "correlation_id": "string",    "data": {},    "id": "string",    "object": "event",    "occurred_at": "2019-08-24T14:15:22Z",    "request_id": "string",    "resource": {      "id": "string",      "object": "string"    },    "type": "string",    "version": 0  }}

List events GET

Lists the public events of the current account. Internal event types are never returned. Results are paginated by cursor and sorted by ID in ascending order unless `sort` specifies otherwise. The collection can be filtered by event type, resource type, resource ID, and occurrence time. Newly recorded events become visible after a short delay of a few seconds, so the most recent events may not appear immediately.

Event streams5

Next Page