DocumentationOpen PingAgain
Browse

Webhook Reference

Signing, retries, and security

Verify signatures, reject replays, and handle retries safely.

Verify every Generic Webhook request before accepting its payload.

Verify a signature

Use the signing secret shown when the destination is created. Compute the signature over the exact request bytes, compare it in constant time, and enforce the timestamp window before parsing JSON.

Record processed delivery identifiers and reject replays. Store the signing secret in a secret manager, not source code or a configuration screenshot. If it is exposed, replace the destination secret and test again.

Retries and history

Return a success response only after your system has safely accepted the event. A non-success response can be retried and appears in PingAgain Delivery history. Make the consumer idempotent so a retry cannot duplicate an external action.

Follow Retry-After or provider wait guidance where applicable. Do not intentionally return errors as a queueing mechanism.

Endpoint security

Webhook endpoints must be public HTTPS destinations allowed by PingAgain’s outbound safety rules. Private networks, unsafe redirects, and disallowed addresses are rejected.

Limit the endpoint to the methods and content types you expect, verify before logging, and keep request bodies out of broad debug logs.

Next: review webhook payloads, Delivery history, or Generic Webhook setup.