---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://www.servicenow.com/docs/r/conversational-interfaces

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Configure Message Authentication for inbound communication

# Configure Message Authentication for inbound communication {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

You can configure Message Authentication for the Virtual Agent API
instead of Basic or OAuth. Message Authentication involves configuring either Static or Hash
tokens, setting up Provider Authentication, and setting the channel identity.

## Before you begin

Follow the steps in [Review the inbound REST endpoint and configure inbound authentication](https://www.servicenow.com/docs/O14Iv3rGMI2TRvEC75JJFw "After you install the Virtual Agent API, navigate to the Scripted REST API resource to review the endpoint and set up authentication.").

Role required:
admin

## Procedure

1. Configure the token by doing one of the following, depending on the token type:
   * Static token:
     1. Navigate to All, and then enter <kbd class="ph userinput">token_verification.list</kbd> in the filter.
     2. Click New.
     3. On the Token Verifications form, fill in the fields.  
        {#set-up-message-auth-va-api__table_lml_hbq_kqb__entry__2}

        | Field | Description |
        |-|-|
        | Name | Name of the authentication token, such as <kbd class="ph userinput">B2BTestAppAuthToken</kbd>. |
        | Description | Description of the authentication token, such as <kbd class="ph userinput">B2B Testing application Auth Token</kbd>. |
        | Token | Enter an authentication token that you generated using any general programming or scripting language, or click Generate Secure Token in the Related Links. |
        [ ]

        {#set-up-message-auth-va-api__table_lml_hbq_kqb}
     4. Click Submit.
     {#set-up-message-auth-va-api__ol_m4d_kcx_v4b}
   * Hash token:
     1. Navigate to All, and then enter <kbd class="ph userinput">hash_message_verification.list</kbd> in the filter.
     2. Click New.
     3. On the Hash Message Verification form, fill in the fields.  
        {#set-up-message-auth-va-api__table_zwd_nbq_kqb__entry__2}

        | Fields | Description |
        |-|-|
        | Name | Name of the authentication token, such as <kbd class="ph userinput">B2BTestAppAuthToken</kbd>. |
        | Description | Description of the authentication token, such as <kbd class="ph userinput">B2B Testing application Auth Token</kbd>. |
        | Secret | Authentication token (random string). |
        [ ]

        {#set-up-message-auth-va-api__table_zwd_nbq_kqb}
     4. Click Submit.
     {#set-up-message-auth-va-api__ol_o4d_kcx_v4b}
2. Set up Provider Authentication for token-based authentication.
   1. Navigate to All, and then enter <kbd class="ph userinput">message_auth.list</kbd> in the filter.
   2. Click New.
   3. On the Message Auths form, fill in the fields.  
      {#set-up-message-auth-va-api__table_ujp_1dp_kqb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name of the message authentication, such as <kbd class="ph userinput">B2B Auth token</kbd>. |
      | Provider | Name of the provider. |
      | Group name | Not required. |
      | Service Portal | Not required. |
      | Inbound message verification | Select the Static token or Hash message token that you created. |
      | Outbound message creation | This field is currently not supported in the Virtual Agent API. Select the Static token or Hash message token that you created. |
      | Outbound service token | This field is currently not supported in the Virtual Agent API. |
      [ ]

      {#set-up-message-auth-va-api__table_ujp_1dp_kqb}
   4. Click Submit.
   {#set-up-message-auth-va-api__substeps_pqj_dqv_4tb}
3. Set the channel identity.
   1. Navigate to All, and then enter <kbd class="ph userinput">sys_cs_provider_application.list</kbd> in the filter.
   2. Select the VA Bot to Bot Provider Application record to open it.
   3. In the Provider Channel Identity form, locate the Message auth field and select the message auth that you set up previously.  
   4. Click Update.
   {#set-up-message-auth-va-api__substeps_wnh_hqv_4tb}
4. For Hash token-based authentication only, send the x-b2b-signature in the request headers.  
   The value is the HmacSHA1 encoded value of the request payload, which uses the token created in the ServiceNow instance. For example, in Postman, follow these steps:
   1. In the Headers, set the x-b2b-signature to `{{hashValue}}`.  
   2. In the Pre-request Script area, set the token as follows:  

          pm.environment.set('hashValue', CryptoJS.HmacSHA1(JSON.stringify(JSON.parse(request.data)), '<insert your token>').toString(CryptoJS.enc.Hex));

   {#set-up-message-auth-va-api__substeps_aj4_4rv_4tb}

## What to do next