SAP Concur

Prev Next

Overview

What Clarity syncs

SAP Concur source

Direction

Users (ID, username, email, name, employee number, active / inactive, termination date)

Identity v4.1 GET /profile/identity/v4.1/Users

read

Product entitlements (Expense, Invoice, Request, Travel, …) and who holds them

Entitlements values on each Identity user

read

Role entitlements (Spend role codes, for example EXP_ATTENDEE_ADMIN)

GET /profile/spend/v4/Users/roleCodes

read

Who holds each role, and the role groups (feature-hierarchy nodes, for example US-SALES) a group-aware role is scoped to

Spend User v4.1 GET /profile/spend/v4.1/Users

read

The connector is read-only. It does not create, deactivate or delete users, and does not assign or remove products or roles in SAP Concur.

How authentication works

Identity v4.1 and Spend User v4.1 accept only company-level access tokens (Identity v4.1). Clarity obtains one for you:

  1. On the first credential test, Clarity exchanges your Company UUID and a one-time Company Request Token (plus the App ID and client secret) at https://{region}.api.concursolutions.com/oauth2/v0/token (Company Level Authentication).

  2. SAP Concur returns a 1-hour access token, a 6-month refresh token, and the company’s datacenter location. Clarity stores them and refreshes the token automatically from then on. Every refresh returns a new refresh token, which Clarity saves.

⚠️ The Company Request Token is single-use and expires 24 hours after it is generated. Enter it in Clarity and run the credential test promptly.

If the connection is ever lost (the refresh token is revoked, or no sync runs for 6 months), generate a new Company Request Token and save it in Clarity. That is the only way to re-authorize.

Prerequisites

  • An SAP Concur App ID (client ID) and client secret for an OAuth 2.0 application with these scopes:

    • Identity v4.1 read: identity.user.core.read, identity.user.coresensitive.read (email addresses), identity.user.enterprise.read (employee number)

    • Spend users: spend.user.general.read

  • Who can issue them depends on your SAP Concur edition. Customers with Client Web Services can create an App ID and secret with the OAuth 2.0 Application Management tool, and generate request tokens with the Company Request Token tool, without contacting SAP Concur. On other editions, the application must be registered through SAP Concur (your SAP Concur account team). Check your edition before you start, as registration through SAP Concur can take time.

  • Both tools are typically under Administration → Company → Authentication Admin, and require the Web Services Administrator or Company Administration permission. Menu names can vary by edition.

Step 1 — Identify your region prefix

Clarity builds the API host as https://{region}.api.concursolutions.com, so enter only the prefix:

Prefix

Notes

us

Default

us2, eu2, apj1, glz

Production datacenters

emea

EMEA gateway host

usg

US government (CCPS) datacenter

us-impl, emea-impl

Implementation (sandbox) companies

Source: SAP Concur Base URIs. Any other value is rejected with an error. China-hosted companies use a different domain that this connector cannot reach.

Step 2 — Generate a Company Request Token

Do this step when you are ready to complete Step 3 straight away.

  1. In SAP Concur, open the Company Request Token tool.

  2. Enter the App ID and submit. The page shows your Company UUID and a Company Request Token.

  3. Copy both. The request token expires in 24 hours.

Step 3 — Enter the credentials in Clarity

In Clarity, add an SAP Concur integration and fill in:

Clarity field

Value

Region

The prefix from Step 1. Defaults to us.

Client ID

The App ID of your SAP Concur OAuth 2.0 application.

Client Secret

The client secret of that application.

Company UUID

The Company UUID from Step 2.

Company Request Token

The request token from Step 2. Single-use; masked.

Click Next, this will trigger our Test Credentials function. The first test performs the token exchange and reads one user from Identity v4.1.

Step 4: App Settings

Complete the App Settings form.  Details for each field can be found at the following article: Common App Configuration Steps

Step 5: User Settings

Complete the User Settings form.  Details for each field can be found at the following article: Common App Configuration Steps

Step 6: Validate Your Selections and Save

Validate the selections from Configure App Step 3, and hit the Save button.

Save Button

Clicking the Save button will trigger the first full sync for your application (even if you selected Manual syncing).

Troubleshooting

Symptom

Likely cause

“SAP Concur did not issue a company-level access token”

The request token was already used, has expired (24 hours), or was generated for a different App ID; or the Company UUID, Client ID or Client Secret is wrong. Generate a new request token and save it.

HTTP 401

The token was rejected. Generate a new request token.

HTTP 403

The application lacks the Identity v4.1 or spend.user.general.read scopes. After SAP Concur adds them, generate a new request token so the token carries the new scopes.

HTTP 404 / host not found

Wrong Region prefix for the company’s datacenter.

HTTP 429 / 5xx

SAP Concur is rate limiting or temporarily unavailable. This is not a credential problem; retry later.

Users have no email

The token lacks identity.user.coresensitive.read, or the users have no email in SAP Concur.

What Clarity does NOT do

  • No provisioning. Clarity does not create, deactivate or delete SAP Concur users, and does not assign or remove products or roles.

  • No China-hosted companies. The connector only reaches *.api.concursolutions.com hosts.

Need Help?

If you have any problems, contact your customer success team. You can also get in touch with our general support via email, open a support ticket. Our general support team is available Monday - Friday from 8:00 AM - 6:30 PM CST.