---
schema_version: "1"
id: a5f84873ff41883b64ec926adb712a21bd6bc0d1068674add2a64c0467d37061
title: Configuring an HTTPS Endpoint
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/https-reference.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/https-reference
source_site: docs.mulesoft.com
content_type: documentation
content_hash: c0a9de0c72e9119be5807ad394f7c2b7ff1920fc54b51f244710efd8af0f89d6
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
keywords: configure, HTTPS endpoint
---

# Configuring an HTTPS Endpoint

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

You can automatically deploy an API proxy using an HTTP listener (inbound HTTP endpoint) with
minimal setup. You can use this approach if you do not foresee any security concerns in your
Anypoint Platform API setup. Otherwise, you must configure your API proxy with an HTTPs listener
(inbound HTTPS endpoint), instead of an HTTP listener.

MuleSoft requires that you provide your own certificate when configuring your HTTPs setup. The
certificate you use can be:

- A self-signed certificate to be used for demo purposes

- A custom TLS certificate with validity within your organization

- A trusted Certificate Authority (CA) certificate

If your backend uses HTTPS with a self-signed certificate or custom TLS certificate, you must
configure the API proxy requester with the corresponding certificate.

Depending on your business use case, you can use any of the following recommended ways to configure
your API proxy:

- [Use a certificate configured through the UI by leveraging Secrets Manager](https://docs.mulesoft.com/api-manager/latest/building-https-proxy):

  Upload your certificate to a secure vault within API Platform, make it available when you
  configure the proxy through the secrets manager, and then deploy the secure API proxy to the
  target runtime, such as CloudHub, Runtime Fabric, or on-premises deployment.

- [Use a certificate defined in already deployed Mule domain](https://docs.mulesoft.com/api-manager/latest/proxy-domain-support)

  Configure the certificate in the domain so that the API proxy HTTPS Listener references it, and
  then deploy the secure API proxy to the target Runtime Fabric, or on-premises target. (CloudHub is
  not supported with this approach because it does not support Mule domains.)

- Use a certificate configured with Anypoint Studio

  For this approach, download the API proxy, open it in Anypoint Studio, and
  [manually configure HTTPS](https://docs.mulesoft.com/mule-runtime/latest/build-an-https-service). You can then deploy
  the proxy to the target runtime, such as CloudHub, Runtime Fabric, or on-premises deployment. (If
  the target runtime is on CloudHub, use port 8082 when working with HTTPs.)

## See Also

- [Build an HTTPS Service](https://docs.mulesoft.com/mule-runtime/latest/build-an-https-service)

- [Building an HTTPS API Proxy](https://docs.mulesoft.com/api-manager/latest/building-https-proxy)

- [Secrets Manager](https://docs.mulesoft.com/anypoint-security/index-secrets-manager)

- [Domain Support for Mule 4 API Proxies](https://docs.mulesoft.com/api-manager/latest/proxy-domain-support)

- [Shared Resources](https://docs.mulesoft.com/mule-runtime/latest/shared-resources)