> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qonto.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proxy API requests from the Embed SDK

> Learn how to proxy API requests sent by our Embed SDK.

The [dispatch endpoint](/api-reference/business-api/endpoints/encoded-requests/dispatch) is designed to be called by your backend to proxy API requests generated by our Embed SDK.

<Note>Only use this endpoint if you're integrating with the Embed SDK. If you're connecting directly to our API endpoints, you can safely skip this section.</Note>

When proxying these requests, you may need to add specific authorization headers. For example, requests sent to our staging environment require the `X-Qonto-Staging-Token` header — see [Accessing the Sandbox environment](/get-started/general/sandbox-access).

These headers, and any similar sensitive information, must not be exposed to the client. They are intended solely for backend use.

To handle this, implement a proxy endpoint in your backend. This endpoint should:

* Receive the request from the client.
* Add the necessary headers.
* Forward the request to our encoded requests dispatch API.

Our dispatcher will then:

* Receive and decode the request.
* Forward it to the appropriate endpoint.

The response returned to your backend is Base64-encoded. Simply return this response to the client as-is, our SDK will handle the decoding for you.
