Solved

Webhook Authorization Token & Raw Request Body

  • 13 February 2024
  • 2 replies
  • 37 views
support.tai-software
Badge

Hello,

We are currently building an integration with Front that will utilize Webhooks. In the “Verifying Integrity” portion of the setup on step 4 it states to “Apply the hmac SHA256 algorithm using the token provided during webhook configuration as the key [output in base 64].”

Where do we get this token? 

The basic information tab only lists the App UID and App Secret while the OAuth tab only lists the Client ID and Client Secret. Are one of these to be used as the token or does it come from somewhere else.

Second, it also says to use the raw request body. I was hoping to confirm what the expected value of the raw request body should look like.

 

"{\"type\": \"sync\",\"authorization\": {\"id\": \"cmp_abc\"}}”

or 

{\u0022type\u0022: \u0022sync\u0022,\u0022authorization\u0022: {\u0022id\u0022: \u0022cmp_abc\u0022}}

 

Thanks!

icon

Best answer by jason 13 February 2024, 17:35

View original

2 replies

jason
Userlevel 4
Badge +7

Hi there,

The token you use to validate request integrity is the App secret from your Developer > App page;

 

Regarding the raw request body, yes - on initially configuring the webhook, Front will send you a validation message containing a JSON object with a body that matches;

{
  "type": "sync",
  "authorization": {
    "id": "cmp_abc" # company id you would see from calling the /me endpoint
  }
}

For all subsequent webhook payloads, an x-front-signature header will be included in the request to allow you to validate the authenticity of this request.

Let us know if you have questions!

 

support.tai-software
Badge

Thank you! This worked and we are authenticating successfully.

Reply


Terms & ConditionsCookie settings