Skip to main content
BundleUp is integration infrastructure for SaaS products. Your users connect their accounts (GitHub, Slack, HubSpot, Google Drive and many more) once through BundleUp. After that, your backend calls those accounts with an API key and a connection ID. BundleUp stores the OAuth tokens, refreshes them, applies retries and rate limits, and logs every request. You never handle a user’s access token, never write token-refresh code, and never build an OAuth flow per provider. The diagram reads left to right. An end user connects an account once through BundleUp Auth, and your backend receives a 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.
Not sure which one you need? See Proxy vs Unified API vs MCP.

What it looks like

Once a user has connected their GitHub account, listing their repositories is one call:
That request goes to GitHub with the user’s token attached. If the token had expired, BundleUp would have refreshed it first.

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.