Authentication
These routes are for the merchant dashboard, not for an installed app. Send the merchant’s session token:app_ access token cannot call them, and the install consent route needs the merchant who is
allowed to install on the store.
List the marketplace
featured.
Query parameters
Featured apps lead the explicit sorts (
installs, rating and newest), which is the point of
curation. installs sorts by the live install base, rating by average then count, and newest by
creation time. A relevance search ranks by score instead, so a featured app gets no bonus there.
Response
featured and collections are set by Salesive admins. There is no developer-writable route for
them.Get one app
inReview: true.
Start an install
The ticket
- Single use, expires after 10 minutes, and is bound to the app, the store and the merchant who requested it.
- Only its SHA-256 is stored, never the raw value.
GET /oauth/authorize?ticket=...validates it without consuming it.POST /oauth/authorizewithapproved: trueconsumes it once, creates the installation and returns a redirect URL with an authorization code. The dashboard does not follow that redirect for a marketplace install; it returns the merchant to the listing, and the app completes its own token exchange when it is opened. A missing, expired or already used ticket is refused with400 invalid_ticketand nothing is installed.
scopes is the list that will actually be granted, after the grantable catalog and customer data
gates. deniedScopes explains every requested scope that was dropped. See
Scopes & permissions.
Errors
Next steps
Install flow
The full consent and token exchange.
Webhook deliveries
List, replay and test an app’s deliveries.

