SDK & embeds
The in-app SDK for apps that run embedded inside Reeve — managed AI, cloud storage, live data, and events, all over a single bridge.
SDK & embeds
There are two ways to build on Reeve:
- The HTTP API — call
https://api.meetreeve.comfrom your own backend with an API key. Best for server-to-server integrations and your own products. Start at the API reference. - The in-app SDK — build an app that runs embedded inside the Reeve app (in an iframe) and talks to Reeve through a
postMessagebridge. Best for tools your users open from within Reeve. This page covers the SDK.
What the embedded SDK gives you
An embedded app loads inside Reeve and uses the SDK to reach Reeve capabilities without managing its own keys or infrastructure:
| Capability | What it does |
|---|---|
| Managed AI | Generate completions through Reeve's model routing — no provider API keys to manage. |
| Cloud storage | A private key-value store scoped to the organization, for app data. |
| Live data | Query connected platforms (Shopify, Klaviyo, ads, analytics) through one interface. |
| Events | Subscribe to platform events and emit your own. |
The SDK handles the postMessage protocol, authentication, and permission enforcement, so your app code is plain async JavaScript. Because it's an iframe, you can build with any framework (React, Vue, Svelte, vanilla).
Reeve app (parent frame)
└── Your app (iframe)
└── SDK ──postMessage──▶ Reeve bridge
├── Managed AI
├── Cloud storage
├── Live data
└── EventsThe embedded App Platform is in developer preview. The capability surface (managed AI, storage, data, events) is grounded in the SDK, but exact method signatures, permission names, and available data sources may change before general availability — confirm against the current SDK package when you build.
Embedding & navigation
An embedded app can navigate the surrounding Reeve app to its named surfaces — for example Studio, Copy, AdBuyer, Chat, or Calendar — or open an external URL in a new tab. Use the surface routes from the product surfaces, not legacy paths.