connection_id. From then on, your backend sends requests to BundleUp with its API key and that connection ID. BundleUp attaches the user’s access token and forwards the call to the provider.
Three ways to call a connected account
All three use the same connections, the same authentication and the same per-connection rate limit. You can mix them freely.Proxy
Call the provider’s own API, unchanged. You write the provider’s paths and
payloads; BundleUp adds authentication, retries and logging.
Unified API
One request shape across providers in the same category: list repos,
tickets, contacts, files or calendar events the same way everywhere.
MCP
Give an AI agent the provider’s own MCP tools, scoped to one user’s
account, without the agent ever seeing a token.
What it looks like
Once a user has connected their GitHub account, listing their repositories is one call:Who BundleUp is for
- SaaS teams that need to read or write data in their customers’ tools and don’t want to run OAuth, token storage and refresh for every provider.
- AI product teams whose agents need to act in a user’s Slack, Linear or GitHub on that user’s behalf.
- Teams with many integrations that want one place to see every outbound call, its status and its latency.
Start here
Why BundleUp
What you would otherwise build yourself, and what you keep control of.
How it works
The moving parts, and what happens to a single request.
Quickstart
From sign-up to your first API call in about five minutes.
Core concepts
Workspaces, integrations, connections and requests.

