Skip to main content
The Proxy lets you call a provider’s API exactly as its documentation describes, as if you were calling it directly. You change the base URL to https://proxy.bundleup.io and add two headers. BundleUp attaches the user’s access token, refreshes it when needed, retries safe requests that fail, and logs the call.

​
When to use the Proxy

  • You need a provider-specific endpoint, field or feature.
  • You’re writing data (creating issues, sending messages, updating records) beyond what the Unified API offers.
  • You already have code against a provider’s API and want to stop managing tokens.
  • You integrate deeply with one or two providers and don’t need a shared data shape.
If you want the same request to work across many providers in a category, look at the Unified API first. See Proxy vs Unified API vs MCP.

​
How it works

BundleUp takes the path and query string of your request, puts them on the provider’s base URL (which it knows from the connection’s integration), swaps your Authorization header for the user’s token, and sends it. The provider’s response comes back to you as-is.

​
What the Proxy does

  • Routes to the right provider based on the connection, not the URL. The same path on two connections can go to two different providers.
  • Authenticates with the user’s access token, refreshing it first if it’s expired or about to expire.
  • Retries GET, HEAD and OPTIONS requests on timeouts, 429, 502, 503 and 504. See Retries.
  • Rate-limits each connection to 100 requests per 60 seconds. See Rate limits.
  • Times out a provider call after 20 seconds (10 seconds for each retry).
  • Logs every call with status and duration. See Logs.

​
What the Proxy doesn’t do

  • It doesn’t change the response. Status, headers and body are the provider’s. Provider errors reach you unchanged, so you handle them exactly as the provider documents.
  • It doesn’t validate your request. Paths, query parameters and bodies go to the provider as you sent them.
  • It doesn’t store bodies. Neither requests nor responses are logged.

​
Next steps

Making requests

Methods, headers, bodies, GraphQL and binary data.

Retries

Which requests are retried, and how to change it.

Rate limits

The per-connection limit and how to handle 429s.

Proxy reference

The endpoint, headers and errors.