> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/getting-started/integration-patterns/proxy-pass.md).

# Proxy Pass

The proxy pass pattern on Pandium: call a third-party API through a tenant's authenticated connector using the Pandium API proxy endpoints, with no sync and no data transformation.

Proxy pass is a straight passthrough. A call hits Pandium and is relayed to the underlying third-party API almost untouched. Pandium injects the tenant's credentials, forwards the request, and returns the response as-is. It does not transform the data on the way through.

<figure><img src="https://4017407078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MfJn-9R_dn6dvcGNcdk%2Fuploads%2Fgit-blob-2b282e3ab33f82646c946632f083cadfba65b260%2F05-proxy-pass.png?alt=media" alt="A caller sends a request to the Pandium proxy layer, which injects auth and forwards the same request to your API, returning the response unchanged"><figcaption></figcaption></figure>

## How it works on Pandium

The [Pandium API](https://docs.pandium.com/reference/pandium-api.md#proxy-endpoints) exposes three proxy endpoints per tenant connector:

| Call type | Endpoint                                                        |
| --------- | --------------------------------------------------------------- |
| REST      | `POST /v2/tenants/{tenant_id}/connectors/{connector_name}/call` |
| SOAP      | `POST /v2/tenants/{tenant_id}/connectors/{connector_name}/soap` |
| XML       | `POST /v2/tenants/{tenant_id}/connectors/{connector_name}/xml`  |

You authenticate to Pandium with your own [API key](https://docs.pandium.com/reference/pandium-api.md#authentication) and tell Pandium which third-party URL, method, headers, and body to send. Because the connector already holds the tenant's authenticated credentials, Pandium adds the authorization the third party expects, refreshing OAuth tokens first if they have expired, and the caller never handles end-user secrets directly. See [Connectors 101](https://docs.pandium.com/connectors/connectors-101.md) for how connector authentication works, and the [NetSuite connector page](https://docs.pandium.com/connectors/connectors-101/netsuite.md#using-the-proxy-api) for a worked example of signing a request through the proxy.

The third party's response comes back to the caller with its status code and body intact. A non-success status from the third party is returned as-is, so the caller can handle it the same way it would handle a direct call.

Proxy calls are rate limited. If your use case needs a higher limit, contact [support](mailto:support@pandium.com). Enterprise plans can raise it to whatever the third-party API itself allows.

## Strengths and trade-offs

Proxy pass is the cheapest pattern to build and run, and callers get the full power of the underlying API. The trade-off is that there is no ETL in the middle and no insulation. The caller has to conform to the third-party API's contract exactly, and any quirks, limits, or breaking changes on that API flow straight through.

Every proxy call is also a synchronous round trip through Pandium to the third party and back. That is fine for a lookup. It is the wrong shape for moving thousands of records.

## When to use it

Use proxy pass when the job is small and tight and you need one piece of data right now, not when you are moving real volume. It is the simplest of the six patterns to stand up, but simple does not mean scalable: under real volume, the extra hops and total reliance on the third-party API's own limits catch up with it. For anything with meaningful throughput, [batch](https://docs.pandium.com/getting-started/integration-patterns/batch-and-api-triggered-syncs.md) is almost always the better fit.

## Real-world examples

* An embedded workflow builder on top of Pandium that needs one value from a connected system right away
* A dashboard pulling a single live figure, like a current account balance, on demand
* A quick one-off lookup where standing up a full sync would be overkill

## Related reading

* [Pandium API: Proxy Endpoints](https://docs.pandium.com/reference/pandium-api.md#proxy-endpoints)
* [Connectors 101](https://docs.pandium.com/connectors/connectors-101.md)
* [Why integration programs need a proxy/passthrough API](https://www.pandium.com/blogs/why-integration-programs-need-a-proxy-passthough-api)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pandium.com/getting-started/integration-patterns/proxy-pass.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
