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
string
required
Display name shown to merchants.
string
Stable identifier. Auto-derived from
name if omitted; must be unique.string
required
Short description shown in the connect UI.
string (https)
required
Public URL of your app logo.
string (https)
Your marketing/site URL.
Contact (required)
The Vambe team uses these to reach you during review and operations.string
required
Your company/organization name.
string
required
Contact email.
string
required
Contact phone number.
OAuth
See OAuth Connection for the full flow.string (https)
required
Where Vambe redirects the merchant to approve scopes.
string (https)
required
Where Vambe exchanges the authorization code for tokens.
string
required
The client id you issued for Vambe.
string
required
The client secret you issued for Vambe. Stored encrypted at rest.
string[]
Scopes requested during authorization.
string (https)
Optional. Lets Vambe fetch the store identity after connection β required for multi-store apps.
Capabilities
string[]
Which canonical events you commit to pushing: any of
order, checkout, fulfillment,
product. See Inbound Webhooks.object
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
1
Iterate (draft)
Update the app while it is
draft or rejected:2
Submit for review
pending_review and notifies the Vambe team.3
Get approved
Once Vambe approves it, the app becomes
approved and is installable by any account.
Until then it is visible only to your account.Other endpoints
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.