Skip to main content

HTTP Processor

The HTTP Processor provides HTTP proxy capabilities to redirect an incoming request from Fusio to another API.




Contains the target URL of your internal API where the request should be redirected. The url can contain also variable path fragments i.e. if your configured Fusio url ist /product/:id you could use as url and Fusio will replace the variable path fragment :id with the provided value. Otherwise all query parameters, headers and body values are proxied to the url.


Describes the Content-Type of the internal API response. Fusio then parses the response and returns the fitting format.


Optional to explicit specify the used HTTP version.


Optional an Authorization header value for internal authorization. You need to provide the complete authorization value i.e. Basic [credentials] or Bearer [my_token].


Optional static query parameters which are always added to the url i.e. in the format foo=bar&key=foo


Optional to enable HTTP caching, this means that Fusio will interpret all HTTP caching headers and cache the response if possible.


Invokes the configured url and passes all provided query parameters, headers and request body to the endpoint. Then it parses the response according to the configured Content-Type and returns the response. Fusio automatically adds some additional headers to the request which may be used by the endpoint i.e.:

X-Fusio-Operation-Id: 12
X-Fusio-User-Anonymous: 0
X-Fusio-User-Id: 4
X-Fusio-User-Name: 4
X-Fusio-App-Id: 3
X-Fusio-App-Key: 1ba7b2e5-fa1a-4153-8668-8a855902edda