API Portal listens for requests on ports that you specify. Each port is associated with a specific type of protocol: HTTP, HTTPS, or email.

By default, the API Portal load balancer component is set to allow both unencrypted HTTP and encrypted HTTPS/SSL access. API Portal has the following pre-configured ports:

API Portal accepts port connection requests as soon as it receives them. If you want to temporarily prevent API Portal from accepting requests on one of its ports, you can disable that port. This action blocks incoming requests from reaching the API Portal server. When a port is disabled, clients receive an error message when they issue requests to it. Later, you can enable the port. If you stop and restart API Portal, the port remains disabled until you enable it. Disabling a port is a convenient way to eliminate developer access to an API Portal once it goes into production.

The following table lists the ports used by API Portal to communicate with each other: