> For the complete documentation index, see [llms.txt](https://docs.unizen.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unizen.io/api-introduction/security-best-practices-for-integrating-unizen/how-to-integrate-with-a-reverse-proxy.md).

# How to integrate with a reverse proxy

### How to Integrate with a Reverse Proxy:

#### 1. **Selecting a Reverse Proxy Solution:**

Integrators are encouraged to choose a reliable reverse proxy solution that aligns with their specific requirements. Popular options include Nginx, Apache HTTP Server, and cloud-based solutions like AWS API Gateway.

#### 2. **Configuring API Key Handling:**

Proper configuration of the reverse proxy is essential for secure API key handling. Integrators should follow best practices for configuring the proxy to conceal API keys and enforce access controls.

#### 3. **Implementing Secure Communication:**

Ensure that communication between client applications and the reverse proxy, as well as between the proxy and API servers, is secured using HTTPS. This safeguards data in transit and prevents potential eavesdropping.

Disabling CORS in our API endpoints is a deliberate choice aimed at fortifying the security of our digital infrastructure. We advocate the use of a reverse proxy as a secure and effective means to handle API requests, concealing API keys and centralizing security controls. Integrators are encouraged to follow best practices outlined in this documentation to ensure a secure and reliable integration with our API.

By embracing these security measures, we reinforce our commitment to protecting sensitive data, maintaining the trust of our users and integrators, and creating a robust foundation for secure API-driven applications.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.unizen.io/api-introduction/security-best-practices-for-integrating-unizen/how-to-integrate-with-a-reverse-proxy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.