Skip to main content
Access token: The credential a provider issues for a user’s account. BundleUp stores it encrypted and attaches it to requests for you. See Connections. API key: A secret that authorizes your backend’s requests to BundleUp. Sent as Authorization: Bearer .... See API keys & client ID. Authorization flow: The browser flow a user goes through to connect an account. Ends with a one-time code sent to your redirect URI. See Connecting user accounts. BU-Connection-Id: The request header that names the connection a request acts on. See Headers. Callback URL (provider): The URL you register with the provider’s OAuth app: https://auth.bundleup.io/callback. The provider sends users here after they approve. Not the same as your redirect URI. Client ID (BundleUp): Your workspace’s public identifier, used in the authorization URL. Client ID / client secret (provider): The credentials of the OAuth app you registered with a provider. You paste these into a BundleUp integration. Code: The one-time value BundleUp appends to your redirect URI after a successful authorization. Exchange it for a connection ID within 5 minutes. Single use. Connection: One end user’s authorized account at one provider. See Connections. Connection ID: The identifier of a connection. The value you store and send with every request. Edge: BundleUp’s globally distributed network where the Proxy, Unified API and MCP run, close to where requests start. External ID: An optional string of your choosing (usually your user ID) attached to a connection. Identifier: The name you give an integration, such as github. Used as integration_id in the authorization URL. include_raw: A Unified API query parameter. When true, the provider’s original response is returned in _raw alongside the normalized data. Integration: A provider configured for your workspace with your OAuth app credentials and scopes. See Integrations. MCP (Model Context Protocol): An open protocol that lets AI agents discover and call tools. BundleUp forwards MCP traffic to providers’ own MCP servers. See MCP overview. Platform API: The REST API at api.bundleup.io for managing connections, integrations and webhooks. Provider: A third-party service such as GitHub, Slack or HubSpot. Proxy: The pass-through API at proxy.bundleup.io. Forwards your request to the provider’s own API with the user’s token. See Proxy overview. Redirect URI (yours): The URL in your app where BundleUp sends the user, with a code, after they connect an account. Must be registered in the dashboard under Auth. Refresh token: A long-lived provider credential BundleUp uses to get a new access token when the current one expires. Request: One call through the Proxy, Unified API or MCP. The unit BundleUp logs, rate-limits and bills. See Requests & usage. Scope: A permission requested from the provider, such as repo on GitHub. Set on the integration. See Choosing scopes. State: An optional value you pass when starting the authorization flow. Returned unchanged on the redirect so you can check it. Protects against CSRF. Unified API: The normalized API at unify.bundleup.io. One request and response shape per category across providers. See Unified API overview. Webhook: An HTTP POST BundleUp sends to your server when something changes, such as a new connection. See Webhooks. Workspace: The top-level container for integrations, connections, keys, webhooks, members and billing. See Workspaces.