Emitting API Events
Overview
Build event-driven API architectures using outbound webhooks, Server-Sent Events (SSE), and message broker integration. Implement event emission from API mutations, event schema registry, subscriber management, delivery guarantees with retry logic, and event sourcing patterns for maintaining a complete audit log of API state changes.
Prerequisites
- Message broker: Redis Pub/Sub, RabbitMQ, Apache Kafka, or AWS SNS/SQS
- Persistent storage for event log and subscriber registrations (PostgreSQL, MongoDB)
- Webhook delivery infrastructure with retry queue (Bull, Celery, or managed service)
- Event schema registry for versioned event type definitions
- SSE-capable web framework for real-time event streaming to browser clients
Instructions
- Identify event-producing operations using Grep and Read, cataloging every API mutation (POST, PUT, PATCH, DELETE) that should emit events, with event type names following
resource.action convention (e.g., order.created, user.updated).
- Define event schemas for each event type with versioning: include
eventId (UUID), eventType, version, timestamp (ISO 8601), source (service identifier), and data (type-specific payload).
- Implement the event emitter service that publishes events to the message broker after successful API mutations, using the transactional outbox pattern to ensure events are not lost on application crash.
- Build a webhook subscription management API:
POST /webhooks (subscribe), GET /webhooks (list), DELETE /webhooks/:id (unsubscribe), with URL validation, event type filtering, and signing secret generation.
- Implement webhook delivery with HMAC-SHA256 signed payloads, configurable retry policy (exponential backoff: 1min, 5min, 30min, 2hr, 24hr), and automatic subscription deactivation after consecutive failures.
- Add Server-Sent Events endpoint (
GET /events/stream) for real-time event delivery to browser clients, with Last-Event-ID support for reconnection and missed event replay.
- Create a dead-letter queue for events that exhaust all delivery retry attempts, with alerting and manual replay capability.
- Write integration tests covering event emission, webhook delivery with signature verification, SSE stream connection with reconnection, and dead-letter queue behavior.
See ${CLAUDE_SKILL_DIR}/references/implementation.md for the full implementation guide.
Output
${CLAUDE_SKILL_DIR}/src/events/emitter.js - Event emission service with outbox pattern${CLAUDE_SKILL_DIR}/src/events/schemas/ - Versioned event type schema definitions${CLAUDE_SKILL_DIR}/src/events/webhooks/ - Webhook delivery, signing, and retry logic${CLAUDE_SKILL_DIR}/src/events/sse.js - Server-Sent Events streaming endpoint${CLAUDE_SKILL_DIR}/src/routes/webhooks.js - Webhook subscription management API${CLAUDE_SKILL_DIR}/src/events/dead-letter.js - Dead-letter queue handler with replay${CLAUDE_SKILL_DIR}/tests/events/ - Event emission and delivery integration tests
Error Handling
| Error |
Cause |
Solution |
| Event lost on crash |
Application crashes between database commit and event publish |
Use transactional outbox pattern: write event to outbox table in same transaction, poll and publish separately |
| Webhook delivery failure |
Subscriber endpoint unreachable or returns non-2xx |
Retry with exponential backoff; deactivate subscription after 5 consecutive failures; notify subscriber admin |
| Event ordering violation |
Concurrent mutations publish events out of order |
Use partition keys (resource ID) for ordered delivery within a partition; accept out-of-order across partitions |
| SSE connection memory leak |
Server accumulates stale SSE connections without cleanup |
Implement heartbeat comments (:keepalive\n\n) every 15 seconds; detect and close dead connections |
| Schema version mismatch |
Consumer expects v1 event format but receives v2 |
Include version field in event envelope; support simultaneous v1/v2 delivery; deprecate old versions with notice |
Refer to ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error patterns.
Examples
Order lifecycle events: Emit order.created, order.payment_received, order.shipped, and order.delivered events with order details, enabling downstream services (warehouse, email, analytics) to react asynchronously.
SSE live notifications: Browser client connects to GET /events/stream?types=message.received,order.updated and receives real-time event updates with automatic reconnection and Last-Event-ID replay on network interruption.
Transactional outbox: Write the event record to an outbox table within the same database transaction as the API mutation, then poll the outbox table every 100ms to publish events to Kafka, ensuring at-least-once delivery.
See ${CLAUDE_SKILL_DIR}/references/examples.md for additional examples.
Resources
1---2name: emitting-api-events3description: Build event-driven APIs with webhooks, Server-Sent Events, and real-time notifications. Use when building event-driven API architectures. Trigger with phrases like "add webhooks", "implement events", or "create event-driven API".4license: MIT5---6# Emitting API Events
7
8## Overview
9
10Build event-driven API architectures using outbound webhooks, Server-Sent Events (SSE), and message broker integration. Implement event emission from API mutations, event schema registry, subscriber management, delivery guarantees with retry logic, and event sourcing patterns for maintaining a complete audit log of API state changes.
11
12## Prerequisites
13
14- Message broker: Redis Pub/Sub, RabbitMQ, Apache Kafka, or AWS SNS/SQS
15- Persistent storage for event log and subscriber registrations (PostgreSQL, MongoDB)
16- Webhook delivery infrastructure with retry queue (Bull, Celery, or managed service)
17- Event schema registry for versioned event type definitions
18- SSE-capable web framework for real-time event streaming to browser clients
19
20## Instructions
21
221. Identify event-producing operations using Grep and Read, cataloging every API mutation (POST, PUT, PATCH, DELETE) that should emit events, with event type names following `resource.action` convention (e.g., `order.created`, `user.updated`).
232. Define event schemas for each event type with versioning: include `eventId` (UUID), `eventType`, `version`, `timestamp` (ISO 8601), `source` (service identifier), and `data` (type-specific payload).
243. Implement the event emitter service that publishes events to the message broker after successful API mutations, using the transactional outbox pattern to ensure events are not lost on application crash.
254. Build a webhook subscription management API: `POST /webhooks` (subscribe), `GET /webhooks` (list), `DELETE /webhooks/:id` (unsubscribe), with URL validation, event type filtering, and signing secret generation.
265. Implement webhook delivery with HMAC-SHA256 signed payloads, configurable retry policy (exponential backoff: 1min, 5min, 30min, 2hr, 24hr), and automatic subscription deactivation after consecutive failures.
276. Add Server-Sent Events endpoint (`GET /events/stream`) for real-time event delivery to browser clients, with `Last-Event-ID` support for reconnection and missed event replay.
287. Create a dead-letter queue for events that exhaust all delivery retry attempts, with alerting and manual replay capability.
298. Write integration tests covering event emission, webhook delivery with signature verification, SSE stream connection with reconnection, and dead-letter queue behavior.
30
31See `${CLAUDE_SKILL_DIR}/references/implementation.md` for the full implementation guide.
32
33## Output
34
35- `${CLAUDE_SKILL_DIR}/src/events/emitter.js` - Event emission service with outbox pattern
36- `${CLAUDE_SKILL_DIR}/src/events/schemas/` - Versioned event type schema definitions
37- `${CLAUDE_SKILL_DIR}/src/events/webhooks/` - Webhook delivery, signing, and retry logic
38- `${CLAUDE_SKILL_DIR}/src/events/sse.js` - Server-Sent Events streaming endpoint
39- `${CLAUDE_SKILL_DIR}/src/routes/webhooks.js` - Webhook subscription management API
40- `${CLAUDE_SKILL_DIR}/src/events/dead-letter.js` - Dead-letter queue handler with replay
41- `${CLAUDE_SKILL_DIR}/tests/events/` - Event emission and delivery integration tests
42
43## Error Handling
44
45| Error | Cause | Solution |
46|-------|-------|----------|
47| Event lost on crash | Application crashes between database commit and event publish | Use transactional outbox pattern: write event to outbox table in same transaction, poll and publish separately |
48| Webhook delivery failure | Subscriber endpoint unreachable or returns non-2xx | Retry with exponential backoff; deactivate subscription after 5 consecutive failures; notify subscriber admin |
49| Event ordering violation | Concurrent mutations publish events out of order | Use partition keys (resource ID) for ordered delivery within a partition; accept out-of-order across partitions |
50| SSE connection memory leak | Server accumulates stale SSE connections without cleanup | Implement heartbeat comments (`:keepalive\n\n`) every 15 seconds; detect and close dead connections |
51| Schema version mismatch | Consumer expects v1 event format but receives v2 | Include `version` field in event envelope; support simultaneous v1/v2 delivery; deprecate old versions with notice |
52
53Refer to `${CLAUDE_SKILL_DIR}/references/errors.md` for comprehensive error patterns.
54
55## Examples
56
57**Order lifecycle events**: Emit `order.created`, `order.payment_received`, `order.shipped`, and `order.delivered` events with order details, enabling downstream services (warehouse, email, analytics) to react asynchronously.
58
59**SSE live notifications**: Browser client connects to `GET /events/stream?types=message.received,order.updated` and receives real-time event updates with automatic reconnection and `Last-Event-ID` replay on network interruption.
60
61**Transactional outbox**: Write the event record to an `outbox` table within the same database transaction as the API mutation, then poll the outbox table every 100ms to publish events to Kafka, ensuring at-least-once delivery.
62
63See `${CLAUDE_SKILL_DIR}/references/examples.md` for additional examples.
64
65## Resources
66
67- CloudEvents specification: https://cloudevents.io/
68- Server-Sent Events (MDN): https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events
69- Transactional outbox pattern: Microservices.io
70- Webhook best practices: Standard Webhooks specification
gabrielmoreira