HTTP Forward Status Codes

This article helps users understand HTTP Forward Status Codes returned by destination endpoints during HTTP forwarding operations. It provides explanations, common causes, and troubleshooting guidance to help quickly identify and resolve delivery or integration issues.

Overview

HTTP Forward Status Codes indicate the response received from the destination endpoint when the platform forwards an HTTP request. These status codes help determine whether the request was successfully processed or if there was an issue with authentication, payload formatting, endpoint configuration, or destination server availability.

The status code is returned in the HTTP response header from the destination system.

Important Note

HTTP Forward Status Codes reflect the response received from the destination endpoint and may not always indicate an issue within the platform itself. Repeated 4xx errors generally indicate request or configuration problems, while repeated 5xx errors usually indicate destination server-side issues.

What You'll Need

Before troubleshooting HTTP Forward Status Codes, ensure you have:

• Access to the platform logs or reporting dashboard.
• Endpoint configuration details.
• API credentials or authentication information (if applicable).
• Access to the destination API documentation.
• Payload samples for validation and testing.

Step-by-Step Guide

Follow these steps to identify and troubleshoot HTTP Forward Status Codes:

1. Locate the HTTP Forward Status Code
   Review platform logs, delivery reports, or forwarding audit records to identify the returned status code.
2. Validate the Endpoint Configuration
   Confirm the destination URL, HTTP method, and authentication settings are configured correctly.
3. Verify the Request Payload
   Check that the request body contains valid syntax, required parameters, and supported formatting.
4. Review Headers and Content Type
   Ensure headers such as Content-Type and authorization headers match the destination API requirements.
5. Test the Destination Endpoint
   Use tools such as Postman or CURL to manually test the endpoint and validate the response.
6. Review Destination System Availability
   Confirm the destination service is online and accepting requests.

HTTP Status Code Reference

Status Code	Status Type	Status Name	Description
200	Success	Completed / OK	The request completed successfully
201	Success	Created	Resource successfully created
202	Success	Accepted	Request accepted for asynchronous processing
301	Failure	Moved Permanently	Resource moved to a new URI
400	Failure	Bad Request	Invalid request syntax or payload
401	Failure	Unauthorized	Authentication failed or missing
403	Failure	Forbidden	Request denied by destination endpoint
404	Failure	Not Found	Endpoint or resource not found
405	Failure	Method Not Allowed	Unsupported HTTP method used
408	Failure	Request Timeout	Destination timed out waiting for request
415	Failure	Unsupported Media Type	Unsupported payload format or content type
429	Failure	Too Many Requests	Rate limit exceeded
500	Failure	Internal Server Error	Unexpected server-side failure
503	Failure	Service Unavailable	Destination service temporarily unavailable

Having Trouble?

If you encounter issues while troubleshooting HTTP Forward Status Codes, refer to the table below.

What you're seeing	Why it happens	How to resolve it
400 Bad Request	Invalid payload or malformed request	Validate request body and required parameters
401 Unauthorized	Authentication failed	Verify API credentials and IP whitelist settings
403 Forbidden	Access denied or missing permissions	Confirm required permissions and request parameters
404 Not Found	Incorrect endpoint URL	Verify destination URL and API route
405 Method Not Allowed	Incorrect HTTP method used	Confirm the endpoint supports the configured method
415 Unsupported Media Type	Incorrect Content-Type header	Update the payload format and headers
429 Too Many Requests	API rate limit exceeded	Reduce request frequency and retry later
500 Internal Server Error	Destination server issue	Retry request or contact destination provider
503 Service Unavailable	Destination service unavailable	Wait and retry after service recovery

Tips for Success

To reduce HTTP forwarding failures and improve delivery reliability, follow these recommendations.

Common Pitfalls

• x Using incorrect endpoint URLs. 
• x Sending invalid or malformed JSON payloads. 
• x Using unsupported HTTP methods. 
• x Configuring incorrect Content-Type headers. 
• x Exceeding destination API rate limits. 
• x Missing required authentication or authorization parameters.

Best Practices

• ✓Validate payloads before sending requests. 
• ✓Use the correct HTTP method supported by the destination API. 
• ✓Review API documentation before configuration changes. 
• ✓Monitor logs regularly for recurring status codes. 
• ✓Implement retry logic for temporary failures such as 408, 429, and 503. ✓Keep API credentials and endpoint configurations up to date.  

Frequently Asked Questions

Q: What does a 200 HTTP Forward Status Code mean?

A: A 200 status code indicates the destination endpoint successfully received and processed the forwarded request.

Q: What causes a 415 Unsupported Media Type error?

A: This usually occurs when the request Content-Type header does not match the format supported by the destination endpoint.

Q: Are 5xx errors caused by the platform?

A: Typically, 5xx errors indicate an issue on the destination server or external service rather than the platform itself.

Q: Which HTTP status codes are usually retryable?

A: Temporary failures such as 408, 429, 500, and 503 may succeed after retrying the request.

Need More Help?

If you continue experiencing HTTP forwarding issues after following the troubleshooting steps above, please contact Support for further assistance.

• Contact Support Submit a ticket to our team for personalized help.