502 - Bad Gateway
Description
The server, while acting as a gateway or proxy, received an invalid response from the upstream server. This indicates a temporary failure in communication between the API server and upstream services or infrastructure components needed to process your request.
Common Scenarios
Upstream server error : The backend service that handles the request is temporarily unavailable or returning errors.
Network connectivity issue : A network problem between the API gateway and upstream services is preventing communication.
Upstream service timeout : The upstream server took too long to respond, causing a timeout on the API gateway.
Load balancer misconfiguration : The load balancer is unable to route the request to a healthy backend server.
Resolution Steps
Retry the request after waiting a few seconds, as the issue may be temporary.
Check the API status page to see if there are known issues with the service.
Verify your request is valid and properly formatted, as upstream errors can sometimes be triggered by invalid input.
If the problem persists, contact support with details about the request and the exact time the error occurred.
Implement automatic retry logic with exponential backoff in your client application.
Refer to the API status page and documentation for information about service health and incident reports.