To receive data, you must first verify your system's endpoint.
If you want to configure endpoints with alternative communication methods or formats, navigate back to the Others tab.
If your organization is configured for multiple regions, an additional field displays for you to designate the region for the endpoint.
If your organization is configured only for one region, this additional field doesn't appear.
https://
.The verification token is a value that you decide and Redox uses in the header of any request you receive to verify that the request is from a legitimate endpoint. Treat it like a password. We recommend you use a unique, long alphanumeric string value that is difficult to brute force or guess.
POST
if your endpoint allows it. However, GET
can be used for verification too. POST
as the verification method, you receive a request with the following payload body:{"verification-token":"[your-verification-token]","challenge":"2e73f864-a0e9-4764-a7d5-91fe5836db22"}
GET
as the verification method, you receive a request with this query string containing two values:?challenge=2e73f864-a0e9-4764-a7d5-91fe5836db22&verification-token=your-verification-token
POST
or GET
request with the challenge value that we provided in the test. You can add the challenge value anywhere in the body of the response.{"challenge":"2e73f864-a0e9-4764-a7d5-91fe5836db22"}