Concur Two-Legged

SAP Concur two-legged auth using a per-company refresh token. App calls Concur as a service identity on behalf of the configured company.

• API category: Concur
• Needs login: No, two-legged: no end-user interaction is required

Configuration parameters

Required

• client_id : string; required
  OAuth client ID for the Concur app.
• client_secret : string; required
  OAuth client secret.
• username : string; required
  Concur company UUID (acts as the username in the two-legged flow).
• password : string; required
  Concur access token used as the password in the two-legged flow.
• initial_refresh_token : string; required
  Long-lived refresh token issued to the integration.

What components can use this API

Concepts:

• API Tester
• API Upload Tester

Ingredients:

• Call API endpoint (in formIngredients)
• Call API endpoint (in rowActionsIngredients)
• Call list API endpoint (in rowActionsIngredients)
• Load list column from API endpoint (in rowActionsIngredients)
• Paginated API GET (in rowActionsIngredients)
• Render as file link (in customShowIngredientsList)
• Render as image (in customShowIngredientsList)
• Set via API call (in setterIngredientsList)