Skip to content

Build and ship plugins on Orbit Commerce.

Task-based walkthroughs for building a plugin end to end, from your first embedded page to a listing on the marketplace. For the exact endpoints and shapes, pair these with the API reference.

Connecting a warehouse or ERP as a supplier? Start with the Supplier API.

  1. Getting startedWhat an Orbit plugin is, and how to build, embed, and authenticate your first one.
  2. Authentication & tokensSession vs access tokens, the install handshake, and where per-store context comes from.
  3. Store API keysConnect a store's own systems to the API with a merchant-minted key. No partner account, no plugin.
  4. OAuth scopesRequest, consent to, and enforce scopes, plus the singular naming convention.
  5. The SDKOrbitClient: typed REST resources, GraphQL, billing, and iframe helpers.
  6. WebhooksSubscribe to events, verify signatures, and handle deliveries reliably.
  7. B2B / ERP integrationSync companies, buyers, and invoices with an ERP: idempotent upserts, silent user provisioning, incremental polling, and two-way webhook sync.
  8. Background jobsWork that runs outside the browser: keeping a credential alive, syncing on a schedule, and handling many stores at once.
  9. Storing your own dataYour plugin's own database: what belongs there, why everything is per store, and the query filter that keeps merchants apart.
  10. Testing your pluginInstall your plugin on a real store with an install link, before it is listed or reviewed.
  11. Publishing your pluginSubmit through the partner dashboard and get listed on the marketplace.
  12. MCPAI assistants and the Model Context Protocol at Orbit: the developer, merchant, affiliate and partner surfaces, and where each one stands.