For the complete documentation index, see llms.txt. This page is also available as Markdown.

Event list

Retrieves a paginated list of available system events and their variables. This is useful for understanding what events can be used in notifications or webhooks and what data they provide.

Endpoint

GET/v2/messages/events

Link

Request

Query Parameters

Parameter
Type
Description
Required
Example

meta.page

integer

Page number (starts from 0).

No

0

meta.pageSize

integer

Number of items per page.

No

20

Headers

Key
Value
Required

Authorization

Bearer <JWT>

Yes

Accept

application/json

Yes


Response (200 OK)

Returns a paginated list of events with their available variables.

Response Fields

1. Meta Object

Field
Type
Description
Example

pageSize

integer

Items per page.

20

page

integer

Current page number.

0

total

string

Total events available.

"45"

2. Event Object (items[])

Field
Type
Description
Example

id

integer

Unique event identifier.

101

Name

string

Event name (descriptive).

"customer.created"

variables

array

Available data variables for this event.

-

Variable Object

Field
Type
Description
Example

name

string

Variable name available in event payload.

"customerId"

Example Response:

json


Examples

Request

bash

Request with Pagination

bash


Common Event Types

  • Customer Events: customer.created, customer.updated, customer.verified

  • Payment Events: payment.initiated, payment.completed, payment.failed

  • Account Events: account.created, account.balance.updated

  • System Events: system.maintenance, system.update


Error Responses

  1. Unauthorized:

    json

  2. Invalid Page:

    json


Notes

  • Usage: These events can be used for webhooks, email templates, or system notifications.

  • Variable Access: In templates, use {{variableName}} syntax to access these variables.

  • Pagination: Default pageSize is typically 20-50 items.

  • Real-time: This list may change as new features are added to the system.

Real request example

Real response example

200 OK

Last updated