---
schema_version: "1"
id: cf78203c290c4a93b7961c196b218841f5ea9aefb287e7efcf42170b646e694a
title: Using API Catalog CLI with a Network Proxy
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/exchange/apicat-use-proxy.md
canonical_url: https://docs.mulesoft.com/exchange/apicat-use-proxy
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 770ca3388df10247da44d3c41300b7c668e89b13096e3179eb9a6e8570603b02
description: MuleSoft Documentation Site
latest: true
---
---
product: Exchange
---

# Using API Catalog CLI with a Network Proxy

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

API Catalog CLI can be run through a network proxy to add a layer of security. To use the API
Catalog CLI with a proxy server, configure the `HTTP_PROXY` or `HTTPS_PROXY` environment variables
with the hostname or IP addresses of your proxy servers as shown in the following sections.

## Configure a Proxy Server Without Authentication

To configure a proxy server that does not require authentication, use the following commands:

- Linux, macOS, or Unix

  `$ export HTTP_PROXY=http://_proxy-server_:80`

  or

  `$ export HTTPS_PROXY=https://_proxy-server_:443`

- Windows

  `> set HTTP_PROXY=http://_proxy-server_:80`

  or

  `> set HTTPS_PROXY=https//_proxy-server_:443`

## Configure a Proxy Server With Authentication

To configure a proxy server that requires authentication, use these commands:

- Linux, macOS, or Unix

  `$ export HTTP_PROXY=http://_username_:_password_@_proxy-server_:80`

  or

  `$ export HTTPS_PROXY=https://_username_:_password_@_proxy-server_:443`

- Windows

  `> set HTTP_PROXY=http://_username_:_password_@_proxy-server_:80`

  or

  `> set HTTPS_PROXY=https://_username_:_password_@_proxy-server_:443`