Verification Status
Learn how to get your app verified by Yoto
When you create a new Yoto app, it starts as unverified by default.
If your app is unverified, users will see a warning on the Yoto consent screen during login, and your developer email will be visible so users know who made the app.
Users (and yourself) can still use your app, but they must explicitly accept the warning before granting your app access to their account.
Your app can remain unverified while you’re doing development, early testing, and small-scale distribution.
Most apps intended for broad public use should eventually be verified. However, apps using scopes that can’t be approved at verification can still remain unverified and still be shared publicly.
Get some usage before you submit
Verification isn’t a requirement to start building, testing, or sharing your app with early users at a small scale.
When you plan to promote your app to a broad public audience, verification can be the next step. We’d rather see apps that already have some real usage behind them than ones submitted the moment they’re technically working.
Our stance on AI-generated apps
Human creativity is at the heart of Yoto, and that extends to the apps built on our platform.
AI can be a great help along the way, but we want to see your own care and progress in the result.
As stated in the previous section, verification is not a requirement, so take the time to test, use, and refine your app before submitting it.
If an app looks like it was generated almost entirely by AI with little human input, testing, or iteration, we’re unlikely to verify it.
Getting your app verified
To start the process, complete the verification form at yoto.dev/verify. We’ll contact you if changes are needed.
We’ll aim to get your app reviewed as soon as possible, but we can’t guarantee review time because it heavily depends on volume. We give preference to apps with an active user base.
Once your app is verified:
- The warning is removed from the consent screen
- Your developer email is no longer shown to users
- Your app will be listed on our developer hub
- The scopes approved during review are locked
If your app is not approved, you can resubmit at any time using the same process.
How to prepare for review
You should submit for review once your app is functional, your requested scopes are final, and your user-facing information is ready.
Before you submit your app, make sure:
- Your app is working as described
- You request only the scopes you genuinely need
- Your developer information on the Developer Dashboard is accurate and up to date
- Your privacy policy is available and reflects how you handle user data
If your app asks for more access than it needs, or if the purpose of that access is not clear, that is likely to delay verification.
If you need help choosing the right permissions, see API Scopes.
Changing scopes after verification
If you need access to different scopes after your app has been verified, contact us before making changes. Your verified app will remain unchanged while we discuss the update.
If you want to test new scopes in the meantime, create a separate app for development and testing.
Scope changes on a verified app will require another review.