Endpoint Configuration Reference

You configure the inbound endpoint of an API so that Anypoint Platform can manage it, either directly or by proxy. The proxy is an application that serves to stop attacks aimed at the actual server.

In Status on the API version details page of an API, click Configure Endpoint. The following configuration sets up a proxy and deploys it to CloudHub.


Endpoint with a Proxy or Basic Endpoint

Configure a basic endpoint if you create your API outside API Manager. For example, if you create the API using Mule Runtime, you don’t need a proxy.

On the API version details page, the gray Endpoint Unregistered indicator remains unchanged, unless you have declared an endpoint for an API that you deployed and configured with your organization credentials. When you set up a proxy for the endpoint and deploy the proxy to Mule Runtime or API Gateway Runtime, Anypoint Platform recognizes the API and replaces the original endpoint that you declared on the API Version details page with the proxy endpoint.

If necessary, you can click Configure Endpoint at any time to make an adjustment. If you move your API, changing its inbound endpoint, repeat the previous steps and set up a new proxy for the API based on its new URL.


Identify your API Type as either HTTP, WSDL, or RAML.


Select this option for non-RAML REST APIs. Provide the full URL of the inbound HTTP or HTTPS endpoint. Also, choose this option if you built the API using APIkit, and then, enter the address of the HTTP Listener of your deployed APIkit application in Implementation URI. The application can be running on-premises or on CloudHub. For example: http://localhost:8086/api or


Select this option for SOAP APIs. Provide the source where Anypoint Platform can extract the URL. For example, you can set if your WSDL is available at Choose this option to manage an existing SOAP API. For the Implemention URI option, enter this address:


Select this option if you designed your API using RAML, which includes an API designed using APIkit. Provide the baseUri from your RAML definition.

Implementation URI

The default URI is the baseUri in the RAML definition. If you plan to deploy the API to production, provide the actual inbound URL of the API, not a placeholder URL; otherwise, to simulating calling the API, a placeholder is fine. In the latter case, you can replace the version with a {version} placeholder. For example,{version}/myresource/{version}. If the API is deployed to a private server and you are using a load balancer, use your load balancer endpoint.

Endpoint Status

After you declare your endpoint, Anypoint Platform displays the state of that endpoint using a gray, green, or yellow status indicator.

Endpoint Status Color Description

Endpoint unregistered


Anypoint Platform has never tracked the endpoint for this API version. Either you have entered a URL for an API or proxy that is not yet deployed, or you have declared an endpoint that is hosted somewhere other than an API Gateway and need to proxy that endpoint so that the platform can track it.

Endpoint active


Anypoint Platform is actively tracking the endpoint. Note that the endpoint must be actively tracked by Anypoint Platform in order for governance policies and SLA tiers to function.

Endpoint inactive


Anypoint Platform previously was tracking this endpoint, but the API or proxy application is currently offline. Hover over the status indicator to view a tooltip that indicates the approximate time the endpoint was last tracked.

Troubleshooting Endpoint Tracking

If you deploy your API or proxy, and believe it should be tracked, check that all the following are true:

  • Your endpoint, configured in your API or proxy, does not have any trailing slashes for connection to your Anypoint Platform organization.

  • If you deploy to CloudHub, ensure that you correctly entered the client ID and client secret of your Anypoint Platform organization as environment variables.

If you deployed your proxy to the cloud, your endpoint should match the domain you selected on deployment. If you deployed to an on-premises gateway, your endpoint is likely The Anypoint Platform agent is tracking your endpoint using this URI, but the URI that you expose to developers can differ.

If you are running an on-premises API Gateway on your local laptop, other developers cannot use this endpoint from their machines.

Endpoint of a Proxy

In API Manager, if you download and deploy a proxy, the endpoint is automatically updated on the API version details page to reflect the inbound endpoint of your proxy. API Manager recognizes the proxy URL as a stand-in for your original URL and updates it automatically on this screen. If you deployed your proxy to a cloud gateway, your endpoint should match the domain you selected on deployment. If you deployed to an on-premises gateway, your endpoint is likely The Anypoint Platform agent is tracking your endpoint using this URI, but the URI that you expose to developers may vary according to your use case.

If you are running an on-premises API Gateway on your local laptop, other developers cannot use this endpoint from their machines.

Deploy to a URL that can be accessed securely by third parties and provide the IP address as an entry point for your API in all your documentation. For example, in all documentation for your API, replace with the IP address of the server, such as

You can also download and use a localhost tunnel such as ngrok from You can assess whether this is appropriate for your use case and does not violate your company’s security policies. If you use ngrok, be sure to turn off ngrok when you are finished with the tutorial.

Proxy Settings

The following options set the proxy:

  • Configure Proxy for CloudHub To deploy to CloudHub. This option fixes the port number to a specific value required by CloudHub.

  • Reference User Domain.

    This option requires creation of an API Gateway domain.

    The default is neither option.

  • In Scheme, HTTP (default) or HTTPS.

  • Port and Path

  • In Advanced Options, Response Timeout

    Optionally, customize the response timeout of the auto-generated proxy you are creating for deployment. The Response Timeout option accepts a value in milliseconds.

HTTPS requests use your default JVM HTTPS certificate. If you want to use HTTPS for the HTTP listener of your API proxy, your web server must have a public key certificate, signed by a trusted certificate authority. After you obtain that, you can set this HTTP listener to HTTPS.

If your API returns URLs that provide apps with internal links to other parts of the API, configure the API proxy application to modify the internal links with proxy substitutes. API Manager can then manage traffic to and from the API through the proxy.

In the following example, The links that must be changed are in the payload returned by your API.  Make this payload easier to scan by transforming it into a string. Add a Groovy expression to replace the original base URI of the links for the proxy domain, if there is one.  Add an Expression component into the flow, after the Object to String Transformer. Whe the API returns a link to content in your API’s domain, it is changed to be routed through the proxy.

<https:outbound-endpoint exchange-pattern="request-response" method="POST" address="[message.inboundProperties['http.request']]" doc:name="Request to API"/>
<choice doc:name="Choice">
            <when expression="">
                <file:file-to-string-transformer doc:name="File to String"/>
            <when expression="">
                <scripting:transformer doc:name="Groovy">
                    <scripting:script engine="Groovy"/>
                </scripting:transformer> </when>
                <object-to-string-transformer doc:name="Object to String"/>
</choice> <expression-component doc:name="Replace BaseUri in payload"> <![CDATA[message.setPayload(message.getPayload().toString().replace("", "http://localhost:8083/"));]]>