Event Naming Format
Event names use a path-like structure with forward slashes:Examples
order/createdpayment/completedinventory/updateduser/deleted
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Best practices for naming events
resource/action
order/createdpayment/completedinventory/updateduser/deleted✅ order/created
❌ Order/Created
❌ ORDER/CREATED
✅ order/created
✅ payment/completed
❌ order/create
❌ payment/complete
✅ order/shipped
✅ order/delivered
❌ order/status-changed
order/created
order/updated
order/cancelled
order/shipped
order/delivered
// Subscribe to all order events
await client.subscribe("order/*");
// Subscribe to all events
await client.subscribe("*");