Skip to main content

The review

In this page you will follow a version from submission to release, and see what is checked on the way.

The life of a version​

FromActionTo
draftSubmitsubmitted
submittedApprove (reviewer)released
submittedReject (reviewer)rejected
submittedWithdrawdraft
rejectedReopendraft
  • A version is edited only while it is a draft. Its number is major.minor.patch and is unique within the app.
  • Submit needs the partner agreement accepted, the listing complete in French and in English, and a logo. One version per app can be in review at a time.
  • Withdraw takes a submitted version back to draft. Reopen does the same for a rejected one.
  • Reviewers and you can exchange notes on a submitted or rejected version. You are emailed when a version is approved or rejected, and when a reviewer writes a note.

Automated checks​

They run when you submit and their results show on the version. Each result is pass, warn or fail. They inform the reviewer and you; the decision is the reviewer's.

CheckWhat it verifies
manifestThe manifest is valid against schema v1; its handle is the app's; every URL (install_url, app_url, support_url, privacy_url, redirect_urls, webhook URIs) is HTTPS, without credentials, on a public host; no write_* scope; at most two extensions per slot; a product tab asks for read_products
install_urlA GET on it answers with a status below 500
app_url_framingFor an embedded app: app_url answers 2xx with a Content-Security-Policy that has frame-ancestors, and does not allow *
endpointsapp_url, install_url, every redirect URL and webhook URI are HTTPS (port 443 if a port is given), resolve in DNS, and not to a private network
listingThe French and English listings are complete and the logo is ready; a missing screenshot is a warn

The checks call your URLs over HTTPS with a 5-second timeout, follow at most three redirects, and send User-Agent: Foodpilot-Marketplace-Review/1.0.

Manual review​

A reviewer installs and uses the app, reads the listing, and approves or rejects the version. A rejection gives at least one reason and a comment:

ReasonMeaning
manifestManifest
scopes_unjustifiedPermissions not justified
listing_qualityListing quality
securitySecurity
privacyPrivacy
brokenThe app does not work
policyPolicy
otherOther

After approval​

The version is released and the app published with the visibility you chose. Platforms where the app is installed are told, and each installation moves to the new version:

  • automatically, when the new version asks for no scope that is not already granted and adds no new destination (a new origin for app_url, install_url, a redirect URL or a webhook, or turning embedded on);
  • after the administrator consents again, otherwise. Until then the installation keeps the previous version and its permissions.

When an automatic update narrows the scopes, your app receives app/scopes_updated.

Suspension and delisting​

  • A suspended app leaves the catalogue and stops working everywhere: its tokens are refused, its webhooks stop, its menu entries and pages disappear. You are told the reason by email.
  • A delisted app leaves the catalogue: no new installs, but installed apps keep working.