### Sign in to App Store Connect [#sign-in-to-app-store-connect-step]
Head to [App Store Connect](https://appstoreconnect.apple.com) and select the correct organization from the top-right dropdown if you have multiple.
### Navigate to Team Key settings [#navigate-to-team-key-settings-step]
Go to **Users and Access** › **Integrations** › **App Store Connect API** › **Team Keys**.
### Generate the key [#generate-the-key-step]
Click the
button and give your key a descriptive name like "Statused API Key".
Choose a role with sufficient access:
* ✅ **Admin** (recommended for full compatibility)
* ✅ **App Manager** (works great)
* ✅ **Developer** (minimum required)
* ❌ **Finance** (won't work)
* ❌ **Sales and Reports** (won't work)
> **Pro Tip**
>
> Go with **Admin** role to future-proof your setup. Apple occasionally updates API permissions, and Admin ensures you won't hit any roadblocks down the line. It may also enable additional features in the future without needing to regenerate keys.
### Download and secure [#download-and-secure-step]
Generate the key and immediately download the private key file (`.p8`). **This is your only chance to download it**, so store it somewhere safe.
## What You'll Need for Statused [#what-you-need]
Your App Store Connect API key has three components — grab all three while you're still in the App Store Connect interface:
* **Private Key File**: The `.p8` file you just downloaded
* **Issuer ID**: Found at the top of the API keys page
* **Key ID**: Displayed in the key list after generation
### Note Your Developer Account ID [#note-your-developer-account-id-step]
Head to [Google Play Console](https://play.google.com/console/?hl=en), click **Account Details**, and write down your **Developer Account ID**. You'll need this to verify you're working with the correct project later.
### Enable the Google Play Developer API [#enable-the-google-play-developer-api-step]
Before creating API keys, you need to enable the Google Play Developer API:
1. Go to [Google Play Developer API](https://console.developers.google.com/apis/api/androidpublisher.googleapis.com/?hl=en) in Google Cloud Console.
2. Choose an existing Google Cloud project or [create a new one](https://console.cloud.google.com/projectcreate/?hl=en).
> **Pro Tip**
>
> Create a dedicated project called "Google Play Console Project" for all your Google Play API needs. This keeps things organized and makes permission management easier.
3. Click ENABLE to activate the Google Play Developer API for your selected project.
### Create a Service Account [#create-a-service-account-step]
> **Best Practices**
>
> If you're already using a service account for tools like *fastlane*, don't reuse it. Create a dedicated one for Statused to prevent API rate limit conflicts and keep your integrations isolated.
1. Open [Service Accounts](https://console.cloud.google.com/iam-admin/serviceaccounts?hl=en) and select the project you want to use.
2. Click
CREATE SERVICE ACCOUNT at the top of the page.
3. Check that you're in the correct project by looking for your **Developer Account ID** in the light gray text before `.iam.gserviceaccount.com`, or check the project name in the navigation bar.
4. Provide a descriptive name like "statused-service-account".
5. Save the generated email address below the Service account ID field. You'll need this later.
6. Click
DONE (don't click
CREATE AND CONTINUE as the optional steps aren't needed).
### Create Your API Key JSON [#create-your-api-key-json-step]
After creating your service account, you'll see it in the service accounts list:
1. Click the button next to your new service account and select Manage keys
2. Click in ADD KEY › Create New Key
3. Ensure JSON is selected as the key type and click CREATE
4. Download and save the JSON file to your computer. Remember the location as you'll need to upload this to Statused.
### Grant Console Access [#grant-console-access-step]
Next, you'll need to connect the service account you just created to Google Play Console.
1. Go to [Google Play Console](https://play.google.com/console/?hl=en) and select
Users and permissions ›
Invite new users
2. Paste the service account email you saved earlier — the one that ends with `.iam.gserviceaccount.com`.
3. Make sure to **not add** any apps to the
App permissions tab.
4. Instead, open the
Account permissions tab and choose appropriate permissions:
* Select only **View app information and download bulk reports (read-only)**
* This provides read-only access, which is all Statused needs and keeps your account secure
> **Here for fastlane?**
>
> If you're here to set up *fastlane* instead of Statused, select **Admin (all permissions)** to ensure full access. This avoids common permission issues when running *fastlane* actions like `supply` or `validate_play_store_json_key`.
6. Finally, click
Invite user and confirm to send the invitation. This completes the setup.
## Next Step: Connect to Statused [#connect]
With your JSON key file ready, you can now connect your Google Play Console account to Statused:
1. Head back to your [Statused dashboard](https://www.statused.com/app) and navigate to
## Create Your Webhook Endpoint [#create-your-webhook-endpoint-step]
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](/integrations/webhooks/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](/integrations/webhooks/security))
> **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](/integrations/webhooks/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 [#add-the-webhook-in-statused-step]
1. Navigate to Destinations › Add Destination in your Statused dashboard
2. Select Webhook
3. Enter your webhook URL
4. **Add a secret token** for verification (strongly recommended)
5. 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 [#test-your-webhook-step]
After adding your webhook, test it to ensure everything works correctly:
1. In your Destinations list, find your new webhook destination
2. Click the menu and select Send Test Notification
3. Check your endpoint logs to verify the test payload was received
### What to Test [#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 [#create-your-workflow-step]
Now connect your webhook to an app to start receiving notifications:
> **Free trial required:** Make sure you've started your trial at [Billing](https://www.statused.com/app/billing) to create workflows.
1. In your dashboard, navigate to Workflows › Add Workflow
2. Give it a descriptive name like `YourAppName Production → Webhook`
3. 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](/email-forwarding).
* Notice that you can see a live preview of your workflow configuration at the bottom of the page, as you configure it.
4. Hit Add Workflow when you're happy with your configuration
## You're Live! What to Expect [#youre-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? [#whats-next]
Now that your webhook is configured, explore these guides to maximize its potential:
- [Secure Your Webhooks](/integrations/webhooks/security) — Implement signature validation and security best practices.
- [Implementation Examples](/integrations/webhooks/examples) — Ready-to-use code for GitHub Actions, CI/CD, and popular frameworks.
- [Webhook Reference](/integrations/webhooks/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](/help) — we're happy to help get your webhooks working smoothly.
# Code Examples (/integrations/webhooks/examples)
Get started quickly with these webhook implementation examples. All examples include proper security validation and error handling.
## Backend Framework Examples [#backend-framework-examples]
> **You're all set!**
>
> Google Play Console emails will now be automatically forwarded to Statused, giving you more accurate app status updates.