Skip to main content

What is the App Platform?

The App Platform lets any ecommerce provider build a first-class integration with Vambe — products, orders, abandoned checkouts, fulfillment and live assistant tools — without Vambe writing any code for you. You register an app, implement a small, well-defined contract, and Vambe handles the rest. It works in two directions:

Inbound — you push to Vambe

Your platform sends canonical webhooks (orders, checkouts, fulfillment, products) to Vambe. Vambe ingests them into the same pipeline used by native integrations.

Outbound — Vambe calls you

When the AI assistant needs live data (order status, stock, a checkout link), Vambe calls URLs you declared, authenticated with the merchant’s OAuth token.

Core model

There are two distinct concepts:
ConceptWhat it isWho owns it
AppThe integration definition you register once: metadata, OAuth config, and which capabilities you support.You (the provider)
InstallationA single merchant connecting their store to your app via OAuth. Each installation holds that merchant’s access token.A Vambe account (the merchant)
One approved app can be installed by many merchants. Every webhook and every outbound call is scoped to a single installation.

How a provider integrates — end to end

1

Register your app

Create the app with your metadata, contact details, OAuth endpoints, and the capabilities you support. You receive a signing secret (shown once).
2

Test on your own account

While unapproved, your app is visible only to the account that created it. Install it on your own store and exercise the full flow.
3

Submit for review

Submit the app. The Vambe team is notified and reviews it. Once approved, the app becomes available to every Vambe account.
4

Merchants connect via OAuth

A merchant clicks Connect in Vambe and is redirected to your site to approve permissions. Vambe exchanges the code for an access token and stores the installation.
5

Data flows both ways

You push canonical webhooks; Vambe calls your capability URLs on demand. No per-provider code on Vambe’s side.

App lifecycle

An app moves through these states:
StateVisible toMeaning
draftCreator onlyBeing built/edited.
pending_reviewCreator onlySubmitted; awaiting Vambe approval.
approvedAll accountsLive and installable by any merchant.
rejectedCreator onlyNeeds changes; edit and resubmit.
suspendedNobodyDisabled by Vambe; stops receiving events and outbound calls.
The connection between a merchant and your app is always OAuth 2.0. Merchants never type API keys into Vambe — they approve scopes on your own page.

Next steps

Create your app

Register the app and get your signing secret.

OAuth connection

Implement the merchant connection flow.

Inbound webhooks

Push orders, checkouts, fulfillment and products.

Outbound capabilities

Answer the assistant’s live data requests.