Apps are different from Themes (your storefront’s look) and Integrations (pre-built
pixel/analytics connectors). An App is your own product, published to the Salesive Apps
marketplace, that any merchant can discover and install.
What you can build
OAuth, not credentials
Merchants grant access through a consent screen. Your app receives a scoped, revocable
token — never the merchant’s login.
Per-store install
Each install binds your app to one store. The token can only ever touch that store’s data.
Work with store data
Read and write orders, products, customers, categories, shipping, discounts and blogs —
gated by the scopes you request.
Publish to the marketplace
Submit your app for review and list it so merchants can find and install it from their
dashboard.
Get events via webhooks
Receive real-time, signed webhook deliveries when store data your app can access changes —
no polling. See Webhooks.
How apps work
1
Register your app
Create an app in the Salesive dashboard’s Developer console (Apps → Developer). You
receive a
client_id and a client_secret, and you declare your redirect URIs and the
scopes (permissions) your app needs.2
A merchant installs it
From the Apps marketplace, the merchant launches your install URL. They’re taken to a
Salesive consent screen that shows the permissions you requested and the store they’re
installing on, and they approve.
3
Salesive issues a token
Your server exchanges the returned authorization code (plus your PKCE verifier and client
secret) for an access token and refresh token, bound to that store and those scopes.
4
Your app calls the API
Send the access token as a
Bearer token on requests to the Salesive API. Salesive
enforces the granted scopes and automatically scopes every request to the installed store.Key concepts
Before you start
You’ll need a Salesive account to access the Developer console (Apps → Developer in your
store dashboard), and a server that can hold your
client_secret and complete the OAuth
token exchange. Apps are headless — Salesive does not host your app’s UI.Next steps
Start from the app starter
Clone a runnable app that already does install, session, webhooks, and the scoped API proxy.
Install flow (OAuth + PKCE)
Implement the end-to-end authorization and token exchange.
Scopes & permissions
See every scope your app can request and how enforcement works.
App Bridge (embedded UI)
Background pre-loading, lifecycle events, and runtime permissions for embedded apps.
Build & publish
Register your app, list it, and submit it for review.
Webhooks
Receive signed, scope-gated store events at your endpoint in real time.