> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spurtcommerce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events

Events communicate that a business action or state change has occurred. Confirm whether the target release uses in-process events, TypeORM subscribers, webhooks, queues, or a combination.

## Event contract

For each verified event, document its exact name, payload schema, trigger point, delivery guarantees, retry behavior, and whether it can be emitted more than once. The repository `.env.example` includes a `SUBSCRIBERS` discovery path (`src/api/subscribers/**/*Subscriber.ts`), which indicates a configured subscriber convention; it does not by itself define public event names.

## Consumer design

Make handlers idempotent, keep them short, isolate failures, and avoid assuming exactly-once delivery. For external side effects, persist processing state or use an outbox pattern if supported by the architecture.

## Verify

Inspect subscriber classes, event emitters/listeners, webhook configuration, queue integration, and tests. Do not publish guessed event identifiers.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.