Webhook workflows

Send App Store notifications to multiple endpoints.

Apple gives each app one production server URL and one sandbox server URL. Use PushTheSales as the receiving endpoint and forward decoded events to your backend and other compatible receivers.

Set up Apple forwarding Read the setup steps ↓
SOURCEApp Store Server Notifications V2
PushTheSalesReceive · normalize · forward
Your backendDecoded JSON
Another receiverDecoded JSON

Separate delivery attempts and environment rules for each receiver.

Illustrative routing diagram · compatible receivers required
THE PROBLEM

Does this sound familiar?

  • Your backend already occupies the Apple notification URL.
  • You need the same event to reach more than one system.
  • A failed receiver needs delivery history and a way to retry.

One Apple delivery URL. Multiple compatible receivers behind it.

THE SETUP

How to make it work.

  1. Check the payload your receivers expect.

    PushTheSales decodes Apple’s signed payload and forwards decoded JSON. It does not preserve the original JWS signedPayload envelope. If a receiver verifies Apple’s original signature or expects that exact envelope, this forwarding flow is not a drop-in replacement.

  2. Create forwarding rules in PushTheSales.

    In Settings, add an Apple forwarding rule for each destination URL. Global rules are useful before products are assigned to an app. App-specific rules take priority over global rules for that provider; configure the complete set of intended receivers at the applicable scope.

  3. Choose the delivery environments.

    Select Production, Sandbox or All for each rule. Use sandbox receivers for test activity and avoid overlapping rules for the same destination, provider and scope. Each receiving URL has its own shared PushTheSales signing key within your workspace.

  4. Test the destination and receiver format.

    Use Test to check the destination response, then verify an actual Apple sandbox notification end to end. The synthetic destination test checks connectivity; it does not prove that your receiver handles Apple data correctly. Your backend can verify the PushTheSales HMAC headers using the destination’s signing key.

  5. Switch Apple’s URLs and monitor delivery.

    In App Store Connect → Apps → your app → General → App Information, set the production and sandbox server URLs to your PushTheSales link with Version 2 selected. Inspect forwarding delivery history, HTTP status and latency. Keep watching real deliveries after the switch.

IN PRACTICE

Recover failed deliveries without guessing what happened.

A delivery record for each receiver.

Inspect attempts, HTTP responses, errors and latency. A failed forwarding attempt does not make the provider ingestion response fail; it remains scheduled for retry.

Automatic retries and manual recovery.

Failed deliveries are retried on the configured schedule. You can retry a delivery manually or replay an inbox event to the currently active rules. Repeated failures or HTTP 410 can disable a rule; correct the receiver and reactivate it.

A signature for your receiving endpoint.

Deliveries include X-PushTheSales-Timestamp and X-PushTheSales-Signature. Verify HMAC-SHA256 of timestamp + "." + the received body with the destination secret. This authenticates the forwarded delivery; it is different from Apple’s original JWS signature.

Questions about this setup.

Can I add two production server URLs directly in App Store Connect?

Apple provides one production URL and one sandbox URL per app. To reach multiple compatible receivers, use a forwarding layer behind that URL.

Will my receiver get the original signedPayload?

No. Apple notifications are decoded before forwarding. A receiver expecting the original signedPayload envelope cannot use this workflow unchanged.

Does a successful Test mean the integration is complete?

No. Test sends a synthetic event. Also verify an Apple sandbox event and the receiver’s actual processing before switching production.

What happens when a receiver is unavailable?

The delivery is retried, with attempts visible in the app. A rule can be disabled after repeated failures or HTTP 410. Once the receiver is fixed, reactivate the rule and retry or replay as appropriate.

PUT IT INTO PRACTICE

One Apple delivery URL. Multiple compatible receivers behind it.

Start in PushTheSales, then follow the setup for your provider.

Set up Apple forwarding