App Store Server Notifications

App Store server notifications are how Botsi finds out about events that happen outside your app: refunds, subscription changes, billing problems. Without them, Botsi's view of a subscription only updates when your app tells it something, which drifts further from the truth the longer the subscription runs.

There are three ways to set this up: send directly from Apple, forward from a platform you already use, or forward from your own backend.

Sending directly from Apple#

In App Settings → iOS SDK in the Botsi dashboard, copy the App Store server notifications URL.
Go to App Store Connect, open your app, and go to General → App Information → App Store Server Notifications.
Choose Edit and paste the URL into both the Production Server URL and the Sandbox Server URL fields.

Both fields matter. A sandbox URL left blank means your test purchases never reach Botsi, which looks identical to a broken integration while production works fine.

Forwarding raw events to your own endpoint#

To keep receiving raw server-to-server events from Apple while using Botsi, add your endpoint to the URL for forwarding raw Apple events field. Botsi forwards those events to your endpoint exactly as they arrived from Apple, unchanged and unmodified.

Forwarding from another platform#

If App Store Server Notifications already route through another platform (RevenueCat, Adapty, or similar), forward those events to Botsi instead of, or in addition to, sending them from Apple. This is the usual setup when an intermediary handles subscriptions or analytics and you still want Botsi to see the full event stream.

In Botsi, copy your App Store Server Notifications URL from App Settings → iOS SDK → App Store Server Notifications.
In the other platform, open its iOS app settings and find the Apple server-to-server notification settings.
Paste the Botsi URL into the field labeled Apple Server Notification Forwarding URL.
Save.

Events forward to Botsi automatically as Apple sends them.

Forwarding from your own backend#

If a custom backend or middleware processes App Store Server Notifications, configure Apple to send events to your system as usual, then forward them to Botsi.

Forward the payload exactly as Apple sent it

Do not modify, decrypt, re-encrypt, or reshape the event. Preserve the full request body, the headers where applicable, and the original JSON structure, then POST it to the Botsi App Store Server Notifications URL.

Botsi verifies and decodes each notification independently using Apple's public keys. A payload that has been touched in transit fails that verification, and the event is discarded rather than partially applied.