Setting Up Your Destination Endpoint

Setting Up Your Destination Endpoint

First, you’ll need to prepare the URL in your application that will act as your Destination Endpoint. This URL will need to be accessible by Redox’s servers and be able to receive both the POST data that is sent when an update happens and also accept GET or POST requests in order to verify the URL with Redox. An HTTPS endpoint is required for both Staging and Production destinations.

Note: SSL certificates for HTTPS destinations cannot be self-signed. Development destinations do not need to be HTTPS.

This URL should return a 200 OK HTTP response when you receive and process messages from RedoxEngine. If there is an issue with the message or you have an issue processing it, you can return a 400 Bad Request HTTP response, which will get logged as an error. In fact, any response code 400 or above will log an error, notifying both you and the Redox team that something went wrong.  Please see our article on HTTP status codes for more information about status codes and the impacts of sending a 400 response.