StatusedConfigure Webhooks
Set up webhook endpoints to receive real-time app store status notifications and automate your release workflow
Ready to start automating your app release workflow? Let's set up your first webhook endpoint to receive real-time notifications from Statused.
Prerequisites
Before setting up webhooks, ensure you have:
- A publicly accessible HTTPS endpoint that can receive POST requests
- Basic understanding of your backend framework for processing webhooks
New to webhooks?
Check out our webhook reference to understand the payload format and event types you'll receive.
Create Your Webhook Endpoint
First, create an HTTP endpoint that can receive POST requests from Statused. The implementation details depend on your stack, but here's what your endpoint needs to handle:
- Accept POST requests with JSON payloads following the CloudEvents specification (see Reference)
- Return 2xx status codes within 30 seconds to confirm receipt
- Handle retries gracefully by being idempotent (we'll retry failed deliveries)
- Validate request signatures using the webhook secret (see Security & Authentication)
HTTPS required
Statused only sends webhooks to HTTPS endpoints. HTTP endpoints without SSL will not receive webhook requests in production.
Need code examples?
Check out our Webhook Examples for ready-to-use code snippets in popular frameworks like Express.js, Ruby on Rails, and Django.
You can also find guides to integrate with CI/CD pipelines and other common use cases not necessarily tied to your backend.
Add The Webhook in Statused
- Navigate to Destinations › Add Destination in your Statused dashboard
- Select Webhook
- Enter your webhook URL
- Add a secret token for verification (strongly recommended)
- Hit Add Destination
Always use secrets
While secrets are optional, they're essential for production security. Without secrets, anyone could send fake webhook requests to your endpoint.
Test Your Webhook
After adding your webhook, test it to ensure everything works correctly:
- In your Destinations list, find your new webhook destination
- Click the menu and select Send Test Notification
- Check your endpoint logs to verify the test payload was received
What to Test
- ✅ Endpoint receives the request
- ✅ Signature validation works (if using secrets)
- ✅ Response time is under 30 seconds
- ✅ Returns appropriate status codes
Create Your Workflow
Now connect your webhook to an app to start receiving notifications:
Free trial required: Make sure you've started your trial at Billing to create workflows.
- In your dashboard, navigate to Workflows › Add Workflow
- Give it a descriptive name like
YourAppName Production → Webhook - Select your API key, app, choose your webhook destination, and fill in the other required details
- For Android apps, we recommend informing us whether Managed Publishing is enabled. More on that in our Google Play Email Forwarding Guide.
- Notice that you can see a live preview of your workflow configuration at the bottom of the page, as you configure it.
- Hit Add Workflow when you're happy with your configuration
You're Live! What to Expect
Monitoring is active
Your workflow is now live and monitoring your app.
The next time your app status changes (submission, review, rejection, live), your webhook will be called, triggering the automated actions you've set up in your backend.
What's Next?
Now that your webhook is configured, explore these guides to maximize its potential:
Secure Your Webhooks
Implement signature validation and security best practices.
Implementation Examples
Ready-to-use code for GitHub Actions, CI/CD, and popular frameworks.
Webhook Reference
Complete payload documentation and event type reference.
Need configuration help?
Webhook setup can be tricky depending on your infrastructure. If you need assistance with configuration or troubleshooting, reach out to us — we're happy to help get your webhooks working smoothly.