Build on top of Behio.
API, SDK and MCP.
The same platform that powers every Behio e-shop is open to you too. A typed Storefront SDK, a public REST API, webhooks and an official MCP server. No reverse engineering, no workarounds.
Four ways to connect.
Storefront SDK
A typed TypeScript client with 60+ methods and 25+ React hooks. Zero-dependency core, optional React bindings.
Public REST API
42 controllers covering the entire catalog, cart, orders and customers. API-key authentication, rate limits per key.
Webhooks
Reliable outbound webhooks with retries. React to orders, payments, restocks and stock movements in real time.
MCP server
An official Model Context Protocol server. Connect Behio to ChatGPT or Claude and run your e-shop through 300 typed tools.
What a developer gets
No hacking around a closed platform. An open, typed surface that is pleasant to build on.
@behio/storefront-sdk from npm
Install it with a single npm command. A zero-dependency core plus optional React bindings, MIT license, no vendor lock.
Typed API with autocomplete
The whole surface is typed from OpenAPI, so your editor suggests methods, parameters and response shapes. You catch errors while typing, not in production.
Real-time webhooks
React to orders, payments and stock movements. Outbound webhooks have retries, so no event slips past you.
Docs at sdk.behio.com
Complete docs with examples, a quickstart and a dedicated MCP server. Plus llms.txt so AI can help you with the integration too.
No exceptions. Just data and error.
Every call returns { data, error } with 19 semantic error codes. The SDK knows when a retry is worth it (5xx, 429, network drop) and refreshes the token in the background.
Developer FAQ
Can I use my own frontend?
Yes. Behio is API-first. Connect your own Next.js, Nuxt or anything else through the SDK and the public REST API and drive the catalog, cart and checkout from anywhere. The storefront does not have to be ours.
What does local development look like?
You install the SDK, generate an API key and call real endpoints right away. Keys are PUBLIC for the browser and PRIVATE for the server, with per-key rate limits, so you test safely.
How do you handle versioning?
We publish the SDK to npm following semver and keep the public API backward compatible. Changes are documented, so you always know what you are building on.