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

# HTTP Proxies

> Route the outbound HTTP requests Alumio makes through a proxy server.

An HTTP Proxy creates a dedicated API endpoint that an external application can call in real time. Alumio acts as the intermediary: it receives the incoming request, optionally transforms it, forwards it to the target system, and returns the response to the caller.

### What HTTP Proxies can do

HTTP Proxies give you control over how requests are handled between the consumer and the target system. You can:

* Forward requests to a target system using a configured HTTP Client and URI.
* Apply processors to modify the request before it is forwarded and the response before it is returned.
* Restrict access using a Matcher to validate that requests come from a legitimate source.
* Override the HTTP status code returned to the consumer using the `HTTP response code` processor.
* Simulate requests using the built-in Configuration tester without needing an external system to trigger the call.

### Filtering HTTP Proxies

The overview page lists all HTTP Proxies in your environment. Filters are available for Name, Created at, Updated at, and Labels. Use **+ Add Filter** for additional conditions. Click any column header to sort.

### Creating an HTTP Proxy

An HTTP Proxy is configured through two tabs: **General** and **Advanced**.

The **General** tab defines the core connection: the target URI, HTTP method, HTTP Client, body parser format, and an optional Matcher to restrict access.

The **Advanced** tab contains processors. Processors let you modify the request before it is forwarded and the response before it is returned to the consumer. Available processors include removing or setting headers, transforming request or response data, and setting a custom HTTP response code.

### Using the Configuration tester

The Configuration tester is available on both the creation form and the detail page. It lets you send a test request in real time. You can configure the method, URI, headers, and protocol, and choose whether to send a real request or simulate one. The Response tab shows the result, including the response body, status code, and headers.

### Custom HTTP status codes

By default, Alumio passes through the HTTP status code returned by the target system. The `HTTP response code` processor lets you override this with a specific status code (e.g. `201`, `202`, `204`), which is then returned to the consumer for all responses from that HTTP Proxy, regardless of what the target system returns.