Replay Safety
Webhook Replays
Review replay policy, idempotency expectations, protected confirmation, original delivery links, and degraded state when durable replay storage is unavailable.
Public-safe Work
- Inspect original delivery
- Review payload summary
- Check idempotency policy
- Open protected-action panel
Protected Boundary
Persistent mutation, third-party delivery, raw private detail, replay, cancel, publish, and sync actions require PLATPHORM_API_KEY.
Authorization: Bearer $PLATPHORM_API_KEY
X-PlatPhorm-API-Key: $PLATPHORM_API_KEYAPI Surface
POST /api/v1/deliveries/{id}/replay protectedPOST /api/v1/deliveries/{id}/cancel protectedGET /api/v1/replaysGET /api/v1/replays/{id}Lifecycle Context
1. Define event type
Name the event, version it, and wrap it in the PlatPhorm event envelope.
2. Define event contract
Attach JSON Schema or an AsyncAPI-compatible event contract before delivery.
3. Register endpoint
Validate endpoint URLs with SSRF protection; server persistence is protected.
4. Generate payload
Create a positive sample, negative sample, or local event payload from a template.
5. Sign payload
Build the canonical string and HMAC header without storing the raw secret.
6. Send event
Protected sends create an event, delivery, async job, attempt, and trace-linked evidence.
platphormctl
platphormctl site inspect webhooksplatphormctl mcp validate webhooksplatphormctl policy inspect webhooksplatphormctl webhooks events