Webhook is not being delivered

Isolation steps

Step 1: Look at the delivery history in the developer portal

Developer portal → App → Webhook → the relevant endpoint → "Delivery history"

Step 2: Checks when there is "no record at all"

• ☐ Is the endpoint "enabled"? (nothing is delivered while it is disabled)
• ☐ Are you subscribed to the relevant event?
• ☐ Are you excluded by the target-store filter?
• ☐ Did the event actually occur? (Is there no delay showing on the status page?)
• ☐ Has the app itself not been suspended / revoked?

Step 3: When it is a "timeout" or "connection failure"

• ☐ Is the receiving URL reachable from outside? (try hitting it from a browser)
• ☐ Is it not behind an internal VPN?
• ☐ Is the TLS certificate valid? (self-signed is not allowed)
• ☐ Does the firewall allow ReceiptRoller's source IPs?
• ☐ Does the receiving handler return 2xx within 10 seconds?

Step 4: When it is "rejected with 4xx"

• ☐ Is signature verification not failing? (returning 401)
• ☐ Is the URL not 404 due to a routing mistake?
• ☐ Is there no implementation-related error in the response body?

Verify with a test delivery

Using the "Test delivery" button in the developer portal, you can send a sample event and verify the receiving side.

1. The relevant endpoint → "Test delivery"
2. Select the event type
3. "Send"
4. Check the receiving side's logs and response code

Redelivering dead letters

After you fix the receiving side, you can manually redeliver from the "Dead letter" filter of the delivery history. It is valid for up to 30 days after the delivery.

Related guides

• Monitoring and handling failures
• Signature verification and security
• Designing resends, ordering, and idempotency
• Back to the developer help index