build-webhook-publisher

To send RFC 9421 signed webhooks from a Go agent, build a webhook.Publisher using webhook.NewSigner with your private PEM, then emit payloads with Publisher.Emit to send signed POST requests securely.

To prevent duplicate webhook deliveries during retries, include an idempotency_key in your payload. This allows receivers to dedupe retries effectively when your publisher resends failed webhook notifications.

To extract subscriber webhook URLs from a push notification config, use webhook.DecodeConfig on req.PushNotificationConfig. This decodes subscriber endpoints and clearly handles any missing or malformed configurations.

Using AdCP compliant webhooks, you can emit asynchronous notifications for task status transitions, resolved list changes, creative artifact batches, and revocation notifications reliably to your subscribers.

Yes, you must preserve webhook payload bytes across publisher retries. Maintaining the exact payload bytes ensures the RFC 9421 signature remains valid and the idempotency_key deduplication functions correctly.

The webhook Publisher handles emitting signed payloads with production retry behavior, while Deliver provides different operational gotchas. Selecting the correct approach ensures reliable asynchronous AdCP notification transmission.