© 2025 Statused. All Rights Reserved.
This page contains answers to the most frequently asked questions. If you have a question that isn’t covered here, don’t hesitate to reach out to us at support@statused.com.
Statused is a service that monitors your Android and iOS apps and notifies your team through Slack or custom webhooks when the apps change review status (e.g. goes into "In Review", "Pending Developer Release", "Rejected", etc.), or when a new version of your iOS app is ready to be tested on TestFlight.
Statused supports Android and iOS apps, regardless of which technology it’s used to build them (e.g. native, React Native, Flutter)
It should also support macOS, watchOS, tvOS, and visionOS platforms, although testing in the wild was limited for these platforms. If you encounter issues when targeting these platforms, please reach out to us and we’ll gladly fix it asap!
Statused is for anyone who submits apps to the App Store or Google Play Store. However, it’s significantly more helpful for teams and not indie developers, because part of the value that it provides is to keep entire teams on the same page.
For QA teams: Be notified when the upcoming iOS app build is available on TestFlight, or when the next Android app version becomes available on internal/alpha/beta tracks, so you can start testing sooner.
For marketing teams: Need to know when a release went out with your ASO updates? Statused logs when it went live with precision.
For project and engineering managers: Be on top of every build that goes out for testing and every release of every app. With searchable history!
The more people you have on your team, the more valuable Statused becomes.
Statused uses the official APIs from App Store Connect and Google Play Developer to monitor the status of your apps and builds. If you’re curious about how these APIs work, you can read more about them in the official documentation for App Store Connect API and the Google Play Developer API.
You need to provide us with the App Store Connect and Google Play Console API keys so we can authenticate with the API on your behalf. We keep your API key secure and encrypted at rest.
Check out Creating API Keys for App Store Connect API official documentation to generate your first API key.
Only the primary Account Owner can enable the creation of App Store Connect API keys in the first place first, for an organization or account.
Once the creation of API keys is enabled and the first API key has been issued, any user with the Admin role can issue new API keys.
The API key needs to have the admin role. We’ve tested with every other role available, but they don’t have enough access to the data we need to monitor the status of your apps and builds.
Check out this blog post 🤖 How to create Google Play API key in 2023 for a step-by-step guide on how to generate your first key.
This question is better answered in detail in the 🤖 How to create Google Play API key in 2023 blog post, but the key here is that Google Play authentication requires two types of configuration: an Account Service in Google Cloud, which doesn’t need any permission at all, and adding the Account Service’s email to your Google Play Console, which requires just the View app information and download bulk reports (read-only) permission.
Statused monitors a few different statuses depending on the platform.
A build status changes when you submit a new build to App Store Connect. It automatically enters the “Processing” state, and when it clears, it goes into “Valid” state.
This is important to identify when new builds become available for internal TestFlight testers, and when it’s ready to be submitted to Apple for review.
The app status, also known as the review status, changes for example when you submit your app for review, or when Apple approves or rejects your app.
This status relates to the status of your App Store Connect organization. This status changes when your account has pending agreements waiting to be accepted, or when previously pending agreements are accepted.
Knowing the status updates of your account is important because while your account has pending agreements, you’re not allowed to submit app updates, and we’re also unable to fetch the status of your apps and builds. Immediate action is required by the Account Holder to avoid disrupting your engineering team’s workflow.
When you submit a new build to one of the tracks (internal, alpha, beta, or production), they go through different statuses, e.g. “In Progress”, “Completed”, “Halted”, etc. Each of these will send a new notification to your team.
The delay between a status change and its notification can be anywhere between 1 and 60 seconds.
The delay between a status change and its notification can be anywhere between 1 and 300 seconds.
The delay is longer than the App Store Connect one due to how Google limits the usage of its APIs. It’s possible to increase the quota limit and thus monitor the status changes with reduced delay. If the delay of up to 300 seconds is a deal breaker to you, reach out to us and we’ll figure out a solution for you.
Yes, Statused sends notifications for phased rollout distribution changes, but only for Android apps.
Statused supports sending notifications to Slack and custom webhooks. We plan to support more notification channels in the future, such as email and Telegram.
If you’re interested in a specific notification channel, don’t hesitate to get in touch with us — this will significantly help us prioritize our roadmap!
Yes, Statused supports Slack Workflows! 🎉
Slack Workflows are a great alternative to Slack Bot’s Incoming Webhooks since they don’t require admin permissions in the Slack organization to be created.
To configure your Statused workflows using webhook URLs from Slack Workflows, follow Slack’s guide on how to Create workflows that start with a webhook, and use the webhook URL that Slack provides to create your workflow in Statused. When configuring your workflow in Slack, use the following variables:
{
message: "The status of your app Launcher for WhatsApp changed to Ready for Sale",
version: "1.2.3",
status: "Ready for Sale",
track: "Production", # Only present for Android apps
user_distribution: "30%", # Only present for Android apps
store_name: "App Store Connect", # Or "Google Play Console"
status_color: "#1eb6fc", # It's e.g. green, yellow, red, depending on the status
app_name: "Launcher for WhatsApp",
app_icon_url: "a URL for your app icon",
internal_store_url: "a URL that points to either App Store Connect or Google Play Console",
statused_url: "https://statused.com",
statused_icon_url: "https://statused.com/assets/logo-grayscale.png",
formatted_datetime: "2023-11-14 16:05:34 UTC",
timestamp: "2023-11-14T16:05:34.474Z",
}
{
message: "The status of build 1.0 (5) of Launcher for WhatsApp changed to Valid.",
version: "1.2.3",
status: "Valid",
store_name: "App Store Connect",
status_color: "#1eb6fc", # It's e.g. green, yellow, red, depending on the status
app_name: "Launcher for WhatsApp",
app_icon_url: "a URL for your app icon",
internal_store_url: "a URL that points to App Store Connect",
statused_url: "https://statused.com",
statused_icon_url: "https://statused.com/assets/logo-grayscale.png",
formatted_datetime: "2023-11-14 16:05:34 UTC",
timestamp: "2023-11-14T16:05:34.474Z",
}
{
message: "Action Needed: You Have Pending Agreements.",
status: "Pending Agreement Acceptance",
store_name: "App Store Connect",
status_color: "#1eb6fc", # It's e.g. green, yellow, red, depending on the status
internal_store_url: "a URL that points to App Store Connect",
statused_url: "https://statused.com",
statused_icon_url: "https://statused.com/assets/logo-grayscale.png",
formatted_datetime: "2023-11-14 16:05:34 UTC",
timestamp: "2023-11-14T16:05:34.474Z",
}
Yes! Statused supports sending notifications to any custom webhook endpoint. This is particularly useful if you want to integrate Statused with your own systems or other third-party services that support webhook integrations, to enable advanced automations.
When configuring a webhook destination, you can provide:
The webhook payloads follow the CloudEvents specification and include detailed information about the status changes. The payload structure of the webhooks looks like this:
{
"specversion": "1.0",
"type": "com.statused.app.status.updated",
"source": "statused",
"id": "6af15d63-dc69-4088-8adf-cdbb7d204eb4",
"time": "2025-01-12T22:12:03Z",
"datacontenttype": "application/json",
"data": {
"message": "The status of your app Launcher for WhatsApp changed to Prepare for Submission",
"version": "1.2.3",
"status": "Prepare for Submission",
"track": null,
"user_distribution": null,
"store_name": "App Store Connect",
"status_color": "#c2c2c2",
"app_name": "Launcher for WhatsApp",
"app_icon_url": "a URL for your app icon",
"internal_store_url": "a URL that points to App Store Connect",
"timestamp": "2025-01-12T22:12:03Z"
}
}
And the valid payload types are:
com.statused.app.status.updatedcom.statused.build.status.updatedcom.statused.account.status.updatedThis is a known limitation from Google’s API that we can’t work around, unfortunately.
The relevant team inside Google was made aware of this issue, and they are interested in resolving it. However, they claim they don’t have enough capacity to work on this for the time being.
If you’d like to help give visibility into this issue, consider +1’ing and commenting on these issues:
Teams from top companies like Lyft, Runway, Shopee, Tramline, Square, Walmart, Skeelo, and your friends from Statused truly appreciate your support.
At the time of writing, Statused monthly plan starts at $8/month, while the yearly subscription earns you 2 months of subscription for free, at $80/year. We also have custom pricing options for bulk app monitoring, which is great for agencies with tons of apps or custom workflows.
Please visit our pricing page for the latest pricing information.
You’ll notice that the subscription is based on workflows. A workflow is a connection between a source (e.g., your iOS app) and a destination (e.g., a Slack channel). You can set up as many workflows as you’d like, which is a great way to separate different types of notifications. For instance, #ios-deploys-prod receives updates about your production app, #ios-deploys-staging receives updates about your staging builds, and #android-deploys-beta receives updates about the Beta track of your Android builds. Each of these is a separate workflow.
We accept all major credit cards. We use Chargebee and Stripe to process payments, so we never store your credit card information.
You can cancel your subscription anytime by visiting the billing page.
You can change your payment method anytime by visiting the billing page.
You can change your plan anytime by visiting the billing page.
We currently support monthly and yearly billing cycles. You can change your billing cycle anytime by visiting the billing page.
Statused uses industry-standard security practices to keep your data secure. All data is encrypted in transit and at rest. We use Chargebee and Stripe to process payments, so we never store your credit card information.
Statused will never share your data with anyone. We will never sell your data to anyone. We will never use your data for any purpose other than to provide you with the service you signed up to receive.
Please visit our contact page to get in touch with us.