How can my endpoint distinguish between a verification POST and a non-verification POST from Redox?
Verification POSTs will include a challenge value and your destination’s verification token (that you specified when you set up the destination record) in the body of the POST. Non-verification POSTs from Redox will always include the verification token in the header of the message.
What are some helpful troubleshooting tips?
Troubleshooting verification with a new destination endpoint will be easier if you first remove encryption and troubleshoot it as an HTTP endpoint, which will give you more insight into the message your endpoint is receiving and your endpoint’s response. Before you remove encryption be sure to set your destination’s verification token to a test value in your dashboard (something like “123”).
I have my app running on my local machine. Can Redox send messages there?
You’ll eventually need a public HTTP server that has the following:
- HTTPS support
- A valid SSL certificate
- An open port that accepts
However, for the purposes of initial testing, ngrok is a free tool that creates a tunnel from the public internet to a port on your local machine. With ngrok installed and configured, POST requests from Redox will be automatically forwarded and responses returned.
In terms of setting up ngrok in a free, non-proprietary way, this guide may also be helpful.