---
sourceDocument: Brazil Financial Services Operations
sourceDocumentLink: https://www.servicenow.com/docs/r/financial-services-operations

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Set up the API REST message

# Set up the API REST message {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure the API REST message for your integration. This step points
outbound REST messages to the correct tokenizer service endpoint.

## Before you begin

Role required: admin

For card network integration, this task requires an OAuth Provider created for Card Data Security. See [Set up an OAuth Provider](https://www.servicenow.com/docs/V58DQrONJXNxQ2a7vV59XQ "Configure an OAuth provider to enable secure authentication between ServiceNow and a third-party tokenizer service for Card Data Security. This setup establishes the necessary connection credentials and JWT configuration required for secure data tokenization operations.") for more information.

## Procedure

1. Navigate to AllSystem Web ServicesOutboundREST Message.
2. Select the REST Message record.
   * For card network integration, select Data Security Vault API
   * For Verifi integration, select Verifi.
3. In the Endpoint field, update the value.
   * For card network integration, enter the `tokenURI` value from the credentials JSON file.
   * For Verifi integration, enter the tokenizer connection URL configured to route Verifi API calls.
4. For card network integration, in Authentication, enter the following field values.

   | Field | Value |
   | Authentication type | OAuth 2.0 |
   | OAuth profile | \<The default profile from the OAuth Provider created for Card Data Security\> |
   |-|-|

   {#set-up-the-vault-api-rest-message__choicetable_lyy_3yy_23c}

## Result

The REST Message record is updated with the correct URL and OAuth profile.

*[\>]: and then