Register an app
Create your app with a single authenticated request. Authentication uses your Vambe API key in thex-api-key header.
signing_secret:
Fields
Metadata
Display name shown to merchants.
Stable identifier. Auto-derived from
name if omitted; must be unique.Short description shown in the connect UI.
Public URL of your app logo.
Your marketing/site URL.
Contact (required)
The Vambe team uses these to reach you during review and operations.Your company/organization name.
Contact email.
Contact phone number.
OAuth
See OAuth Connection for the full flow.Where Vambe redirects the merchant to approve scopes.
Where Vambe exchanges the authorization code for tokens.
The client id you issued for Vambe.
The client secret you issued for Vambe. Stored encrypted at rest.
Scopes requested during authorization.
Optional. Lets Vambe fetch the store identity after connection β required for multi-store apps.
Capabilities
Which canonical events you commit to pushing: any of
order, checkout, fulfillment,
product. See Inbound Webhooks.URLs Vambe calls on demand. Each entry is
{ "url": "https://..." }. Supported keys:
order_get, stock_get, checkout_create. If you omit a key, Vambe simply wonβt offer
that assistant tool for your app. See Outbound Capabilities.Manage and submit
Other endpoints
| Method | Path | Purpose |
|---|---|---|
GET | /api/ecommerce-app | List your apps. |
GET | /api/ecommerce-app/{id} | App detail (no secret). |
POST | /api/ecommerce-app/{id}/rotate-secret | Generate a new signing secret. |
DELETE | /api/ecommerce-app/{id} | Delete the app. |
GET | /api/ecommerce-app/available | Apps installable by the current account. |
Editing an
approved app is blocked β only draft/rejected apps are editable. Editing a
rejected app moves it back to draft so you can resubmit.