Test your app
In this page you will get your app onto one platform to test it, then check it against what the review looks at.
An app is installable once a version is approved
A platform offers an app only when the app is published, which happens when a version is approved. Until then, no platform can install it, whatever its visibility. There is no sandbox that installs drafts.
What you choose is where an approved version is offered:
| Visibility | Who can install it |
|---|---|
private | Only the platforms you name, up to 100 |
unlisted | Any platform, from a link, but it is not listed in the catalogue |
public | Any platform, and it is listed in the catalogue |
The visibility you choose is applied when the version is released, not before.
Test on one platform first
- In the partner space, set the visibility to private and name your test platform.
- Submit the version. The automated checks run at once and their results appear on the version: fix any
failbefore a reviewer looks at it. - Once it is approved, an administrator of your test platform installs the app.
- When you are ready for everyone, change the visibility to
unlistedorpublicand submit a new version.
Checklist before you submit
- Install. Your
install_urlanswers, redirects to the consent page, and yourredirect_urlexchanges the code. A reinstall after an uninstall creates a new installation: do not reuse the old tokens. - Tokens. You refresh the access token before it expires (one hour) and store the new refresh token each time: the old one is revoked, and reusing it revokes the whole family.
- Webhooks. You verify every signature on the raw body, answer
2xxwithin 5 seconds, and handle each event id once. Only a2xxcounts as delivered. - Uninstall. On
app/uninstalledyou stop calling the API for that installation and delete its data. - Embedded pages. Your
app_urlanswers2xxwith aContent-Security-Policywhoseframe-ancestorsnames the platforms' origins, never*. - Scopes. You ask only for the scopes you use. A
product.details.tabextension needsread_products. - Organizations. You treat a
404on a resource as "not granted to you": an app never learns what exists outside its organizations. - Rate limit. You honour
429and itsRetry-After.
Next
- The review: what the checks and the reviewer look at.
- Your listing: what a version needs before it can be submitted.