---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up the SAP Concur spoke

# Set up the SAP Concur spoke {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read  
Integrate the ServiceNow instance and SAP Concur by creating a custom OAuth application in SAP Concur to authenticate ServiceNow requests.

## Before you begin

* Request an Integration Hub subscription.
* Activate the SAP Concur spoke.
* Role required: admin
{#setup-sapconcur-spk__ul_ufp_1rd_h4b}

## Procedure

1. Register SAP Concur as an OAuth provider.
   1. Navigate to System OAuthApplication Registry.
   2. Click New.  
      The system displays the message What kind of OAuth application?
   3. Select Connect to a third party OAuth Provider.  
      The system displays a blank Application Registries form.
   4. On the form, fill these values.  
      {#setup-sapconcur-spk__table_frn_tkd_h4b__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name to uniquely identify the application registry. For example, <kbd class="ph userinput">SAP Concur OAuth</kbd>. |
      | Client ID | Client ID of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. |
      | Client Secret | Client secret of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. |
      | Default Grant type | Grant type used to establish the token. Select Resource Owner Password Credentials. |
      | Token URL | URL from which the ServiceNow instance obtains the access token. Format of the token URL is, <kbd class="ph userinput">https://&lt;host-name&gt;/oauth2/v0/token</kbd>. Here, host name is the fully qualified domain name of the target host where SAP Concur is installed. |
      | Redirect URL | OAuth callback endpoint in this format: <kbd class="ph userinput">https://&lt;instance&gt;.service-now.com/oauth_redirect.do</kbd>. |
      [ ]

      {#setup-sapconcur-spk__table_frn_tkd_h4b}
   5. Right-click the form header, and click Save.  
      * The system validates the OAuth credentials and populates the Redirect URL.
      * The system populates OAuth Entity Profile with Grant Type as Resource Owner Password Credentials. For example, OAuth Entity Profile is created with default Name, SAPConcur
      {#setup-sapconcur-spk__ul_gks_4f4_xgb}
   {#setup-sapconcur-spk__substeps_gyp_mkd_h4b}
2. Create a credential record for the SAP Concur spoke.
   1. Navigate to Connections \& CredentialsCredentials.
   2. Click New.  
      The system displays the message What type of Credentials would you like to create?.
   3. Select OAuth 2.0 Credentials.
   4. On the form, fill these values.  
      {#setup-sapconcur-spk__table_wpg_mmd_h4b__entry__2}

      | Field | Value required |
      |-|-|
      | Name | Name to uniquely identify the record. For example, enter <kbd class="ph userinput">SAP Concur Cred</kbd>. |
      | Active | Option to actively use the credential record. |
      | OAuth Entity Profile | OAuth profile you created when you registered the custom SAP Concur application as an OAuth provider. For example, select SAPConcur. |
      | Applies to | Select the MID Servers that can use this credential. For example, select All MID Servers. |
      | Order | Select the order to apply this credential. For example, enter <kbd class="ph userinput">100</kbd>. |
      [ ]

      {#setup-sapconcur-spk__table_wpg_mmd_h4b}
   5. Save the record.
   {#setup-sapconcur-spk__substeps_h3l_2md_h4b}
3. Create a connection record for the SAP Concur spoke.
   1. Navigate to Connections \& CredentialsConnection \& Credential Aliases.
   2. Open for the record, SAPConcur.
   3. From the Connections tab, click New.
   4. On the form, fill these values.  
      {#setup-sapconcur-spk__table_any_shp_gfb__entry__2}

      | Field | Value required |
      |-|-|
      | Name | Name to uniquely identify the connection record. For example, enter <kbd class="ph userinput">SAP Concur Connection</kbd>. |
      | Credential | Credential record you created for SAP Concur. For example, select SAP Concur Cred. |
      | Connection URL | Connection URL to connect to SAP Concur in this format: <kbd class="ph userinput">&lt;Host&gt;/api</kbd>. |
      | Host | Fully qualified domain name of the target host where SAP Concur is installed. For example, <kbd class="ph userinput">us.api.concursolutions.com</kbd> or <kbd class="ph userinput">eu.api.concursolutions.com</kbd>. |
      | Protocol | <kbd class="ph userinput">https</kbd> |
      | Base path | <kbd class="ph userinput">/api</kbd> |
      [ ]

      {#setup-sapconcur-spk__table_any_shp_gfb}
   5. Click Submit.
   {#setup-sapconcur-spk__substeps_ffz_hmd_h4b}
4. Generate OAuth token by providing the SAP Concur API user credentials.
   1. Navigate to Connections \& CredentialsCredentials.
   2. Open the credential record you had created.  
      Example: SAP Concur Cred
   3. Click the Get OAuth Token related link and provide the SAP Concur API user credentials to generate the OAuth token.
   {#setup-sapconcur-spk__substeps_lqk_gzd_h4b}
5. Configure the connection, SAP Concur Event Subscription Service.
   1. Navigate to Process AutomationFlow Designer.
   2. Click the Connections tab.
   3. Locate the SAP Concur Event Subscription Service connection alias and click View Details.
   4. To configure the spoke for the first time, select Configure or click Edit.
   5. On the Connection form, fill in the fields.  
      {#setup-sapconcur-spk__table_u4n_byy_gxb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name of the connection alias record. |
      | Connection URL | Connection URL in this format: <kbd class="ph userinput">https://www-&lt;Region&gt;.api.concursolutions.com</kbd>. Replace <kbd class="ph userinput">&lt;Region&gt;</kbd> with the appropriate SAP Concur region. |
      | Version | Enter <kbd class="ph userinput">v4</kbd>. |
      | Token URL | Token URL in this format: <kbd class="ph userinput">https://&lt;Region&gt;.api.concursolutions.com/oauth2/v0/token</kbd>. Replace <kbd class="ph userinput">&lt;Region&gt;</kbd> with the appropriate SAP Concur region. |
      | Client ID | Client ID of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. |
      | Client Secret | Client secret of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. |
      [ ]

      {#setup-sapconcur-spk__table_u4n_byy_gxb}
   6. Click Create and Get OAuth Token.

   {#setup-sapconcur-spk__substeps_nvh_sxy_gxb}  
   A confirmation message is displayed that the OAuth token is generated successfully.
6. Configure the connection, SAP Concur v4 APIs.
   1. Navigate to Process AutomationFlow Designer.
   2. Click the Connections tab.
   3. Locate the SAP Concur v4 APIs connection alias and click View Details.
   4. Click Edit or if you are configuring the spoke for the first time, click Configure.
   5. On the Connection form, fill in the fields.  
      {#setup-sapconcur-spk__table_vqr_hzy_gxb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name of the connection alias record. |
      | Connection URL | Connection URL in this format: <kbd class="ph userinput">https://&lt;Region&gt;.api.concursolutions.com</kbd>. Replace <kbd class="ph userinput">&lt;Region&gt;</kbd> with the appropriate SAP Concur region. |
      | Version | Enter <kbd class="ph userinput">v4</kbd>. |
      | Token URL | Token URL in this format: <kbd class="ph userinput">https://&lt;Region&gt;.api.concursolutions.com/oauth2/v0/token</kbd>. Replace <kbd class="ph userinput">&lt;Region&gt;</kbd> with the appropriate SAP Concur region. |
      | Client ID | Client ID of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. |
      | Client Secret | Client secret of your SAP Concur client application. Contact SAP Concur Implementation team to obtain this value. |
      [ ]

      {#setup-sapconcur-spk__table_vqr_hzy_gxb}
   6. Click Create and Get OAuth Token.  
      In a new window, you will be prompted to enter Username and Password.
   7. For Username, provide the Company ID of the SAP Concur instance and for Password, provide the value of Company Request Token.  
      Note:  
      Contact SAP Concur Implementation team to obtain the values of Company ID and Company Request Token.
   8. Click Get OAuth Token.
   {#setup-sapconcur-spk__substeps_uqr_hzy_gxb}
7. Map SAP Concur users to the ServiceNow user in the SAP Concur User Mappings module.
   1. Navigate to SAP Concur SpokeSAP Concur User Mappings.
   2. Click New.
   3. On the form, fill these values.  
      {#setup-sapconcur-spk__table_dsr_tzd_h4b__entry__2}

      | Field | Description |
      |-|-|
      | ServiceNow User | Reference to the user record in the User \[sys_user\] table. |
      | SAP Concur User ID | User ID of the required user in SAP Concur. |
      [ ]

      {#setup-sapconcur-spk__table_dsr_tzd_h4b}
   4. Click Submit.  
      Note:  
      If a user attempts to access data in the SAP Concur Expense Entries module without being mapped to the corresponding SAP Concur User ID in the SAP Concur User Mappings module, this error message is displayed.A user with username adminn does not exist.

      Map the ServiceNow user to the correspnding User ID in SAP Concur too access data in the SAP Concur Expense Entries module.

   {#setup-sapconcur-spk__substeps_cry_qzd_h4b}  
   * SAP Concur spoke is set up.
   * Data is retrieved and displayed in the SAP Concur Expense Entries and SAP Concur Expense Reports modules.
   {#setup-sapconcur-spk__ul_eph_rd2_h4b}

*[\>]: and then