Skip to main content
Point your app’s App Store Server Notifications v2 URL (production and sandbox) at this endpoint in App Store Connect:
There is nothing per-organization in the URL: Grantiva verifies the notification’s JWS signature against Apple’s root CA (Apple Root CA-G3) and routes it to your organization by matching the notification’s bundle ID against your entitlement configuration.

​
What it processes

Subscription lifecycle notifications (subscribe, renew, expire, refund, revoke, grace-period events) for product ids present in your apple.products mapping. The sharing unit is resolved from the transaction’s appAccountToken — which is why your app must set it at purchase time (see the quick start). On each accepted event Grantiva updates the Subject’s entitlement, which changes custom_claims.subscription in subsequently minted JWTs, and fires the corresponding subscription.* webhooks.

​
Response semantics

Permanent conditions intentionally return 200 so Apple stops retrying them. Replay protection is keyed on Apple’s notificationUUID. A request with no body, or a body that is not a signedPayload envelope, returns 400. Every permanent drop that can be attributed to your organization is recorded — read it back from GET /api/v1/org/entitlement-ingest-events.
Sandbox notifications are ingested too, producing claims with "environment": "sandbox". Filter on environment in production backends.