API Reference

Verification Token Configuration

👍

As part of our ongoing commitment to ensuring secure and flexible integrations, Radaro now offers two methods for sending webhook verification tokens

  • Token in body
  • Token in headers
  • Token in body & headers

This enhancement allows for greater compatibility with various systems and preferences in handling security protocols.

Overview

Webhook verification tokens are crucial for securing communication between Radaro and your system. By verifying these tokens, you can ensure that the requests your system processes are legitimate and coming from Radaro. You can find out about integration here

Configuration Options

Upon setting up your webhook integration, you can choose one of the following methods for receiving the verification token:

  1. Token in body (Default).
    By default, Radaro sends the verification token in the body of the webhook request. This method is straightforward and easily accessible, making it the default choice for most integrations.
    Example Payload:

    {
  "token": "MlfqEdN60b9fLOHEPdPGUQ"
}

  2. Token in headers

    For integrations that prefer or require token verification to be handled in the headers, Radaro supports sending the verification token as a part of the request headers.
    This method is particularly useful for systems that process authentication and authorization at the network edge or before the payload is fully received.

    Example Headers:

    {
  "Authorization": "Token MlfqEdN60b9fLOHEPdPGUQ"
}

Setting Your Preference

To configure your webhook verification token preference, please contact the Radaro support team with your chosen method.
If you do not specify a preference, Radaro will use the default method of sending the token in the body.We recommend reviewing your system’s requirements and security policies to choose the method that best suits your integration needs.
The Radaro support team is available to assist with any questions or concerns you may have regarding this configuration.