App Store Connect webhooks are HTTP callbacks that Apple sends to your server endpoint whenever certain events occur in your app's lifecycle. They were introduced at WWDC 2025 as part of Apple's push to make App Store Connect more programmatic.
What events do they cover?
App Store Connect webhooks cover operational events:
- App Version: Review status changes (APP_STORE_VERSION_APP_VERSION_STATE_UPDATED)
- Builds: Build processing state changes (BUILD_UPLOAD_STATE_UPDATED)
- TestFlight: Beta build state and tester feedback (BUILD_BETA_DETAIL_EXTERNAL_BUILD_STATE_UPDATED, BETA_FEEDBACK_CRASH_SUBMISSION_CREATED, BETA_FEEDBACK_SCREENSHOT_SUBMISSION_CREATED)
- Background Assets: Background asset processing and release states
How do they work?
- You configure a webhook URL in App Store Connect (or Yeethook does this automatically)
- Apple sends a POST request to your URL when an event occurs
- Your server validates the HMAC signature
- You process the event and respond with 200 OK
Why use Yeethook?
Setting up webhooks requires:
- A publicly accessible HTTPS endpoint
- HMAC signature validation
- Proper error handling
- Integration with your notification system
Yeethook handles all of this. Just connect Slack and every event arrives as a formatted message. In Quick Start mode, Yeethook even creates and configures the webhooks for you automatically.
Manual vs Quick Start
- Manual Setup: You create webhooks in App Store Connect yourself, Yeethook formats and forwards events
- Quick Start: Upload a p8 key and Yeethook creates webhooks automatically, plus enriches events with API data