Extension Model Overview
BoxNCase is extended through stable, managed interfaces rather than changes to the platform codebase. This keeps your integration isolated, upgradeable, and independently deployable.
Choose an extension surface
| Need | Recommended surface |
|---|---|
| Read or update commerce data | GraphQL API with a least-privilege app token |
| React to a completed platform event | Asynchronous webhook |
| Participate in a pricing, tax, shipping, or checkout decision | Synchronous webhook |
| Add an operator workflow to the Dashboard | App with Dashboard extension points |
| Connect an approved provider | Extension catalog |
Apps
Apps are independently deployed services that use the BoxNCase API and webhooks. An app can also render approved views inside the Dashboard. Its manifest declares identity, endpoints, permissions, webhooks, and Dashboard extension points.
Start with Building Apps.
API access
Server-side integrations use app tokens to read and write only the resources allowed by their assigned permissions. Common uses include inventory updates, order export, catalog enrichment, and customer-system synchronization.
See Authentication and the API reference.
Webhooks
Asynchronous webhooks notify your service after an event. Synchronous webhooks are reserved for supported decisions that must complete during a platform operation. In both cases, verify signatures, make handlers idempotent, and keep response times bounded.
See Webhooks.
Dashboard extensions
Dashboard extension points let an app add a page, widget, action, or modal to a supported location. The app UI runs in a sandboxed frame and communicates with the Dashboard through the App Bridge.