---
schema_version: "1"
id: b50632992113beaf985f45f9b50e978794f4efd3efb73fd6261b2d39e5c25fd2
title: Reviewing API Proxy Benefits and Impacts
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/proxy-advantages.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/proxy-advantages
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7c96d26c9a2bd528179d9dd8be66d12d98753eca6b55c6bfb734523d02cd80e0
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
---

# Reviewing API Proxy Benefits and Impacts

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The tables below describe the main benefits and impacts of implementing the different types of API
Proxies.

## Benefits

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Benefit</th><th>WSDL</th><th>RAML/OAS</th><th>HTTP</th><th>HTTPS</th></tr></thead><tbody><tr><td><p>Tracks proxy in API Manager and generates Mule API analytics. Requires Autodiscovery.</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td></tr><tr><td><p>Applies policies for API governance.</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td></tr><tr><td><p>Sends errors related to MuleSoft-provided policies as soap:fault messages</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>no</p></td><td><p>no</p></td></tr><tr><td><p>Includes API Console for simulating API requests.</p><p>By default, you can open API Console using a URL in the format: <code>&lt;host_of_your_proxy&gt;:&lt;port_of_your_proxy&gt;/console</code></p></td><td><p>no</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>no</p></td></tr></tbody></table>

## Impacts

These are the impacts on your requests going through your API proxies.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Impact</th><th>WSDL</th><th>RAML/OAS</th><th>HTTP</th><th>HTTPS</th></tr></thead><tbody><tr><td><p>Includes X-Forwarded-For headers.</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td></tr><tr><td><p>Sends received headers to implementation API except Mule-included ones.</p><p>Mule-included headers are, for example, X-MULE-SESSION, and X-MULE-ENCODING, among others.</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td><td><p>yes</p></td></tr><tr><td><p>Validates headers, body, URI, query, and form parameters API against RAML 0.8/1.0.</p></td><td><p>no</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>no</p></td></tr><tr><td><p>Provides default parameter values if specified in RAML but absent from request.</p></td><td><p>no</p></td><td><p>yes</p></td><td><p>no</p></td><td><p>no</p></td></tr><tr><td><p>Handles a secure connection using the keystore and truststore provided in the TLS configuration for server authentication.</p></td><td><p>no</p></td><td><p>no</p></td><td><p>no</p></td><td><p>yes</p></td></tr></tbody></table>

## See Also

- [API Console - To Simulate API Calls](https://docs.mulesoft.com/apikit/latest/apikit-4-implement-rest-api)