New260+ blocks and 240+ tools are now fully documented
DocumentationReferenceTool IntegrationsFinance & Payments
Tool

SAP Concur Tools

List and retrieve expense reports and users from SAP Concur via the v3.0 Expense and Common APIs

SAP Concur is an expense, travel, and invoice management platform. Use these tools in a workflow to read expense reports and user records from your SAP Concur tenant via the v3.0 Expense and Common REST APIs — for example, to pull pending expense reports for review, fetch a single report's details, or look up users by email.

Overview

PropertyValue
Providersap-concur
Categorytools
AuthOAuth (Bearer access token)

Operations

OperationTool IDDescription
List reportssap_concur_list_reportsList expense reports from SAP Concur (GET /api/v3.0/expense/reports).
Get reportsap_concur_get_reportRetrieve a single expense report by ID (GET /api/v3.0/expense/reports/{id}).
List userssap_concur_list_usersList users from SAP Concur (GET /api/v3.0/common/users).

All operations authenticate with a SAP Concur OAuth bearer access token sent as Authorization: Bearer {{accessToken}} against https://www.concursolutions.com.

Configuration

sap_concur_list_reports

ParameterTypeRequiredDescription
accessTokenstringYesSecret. SAP Concur OAuth bearer access token (visibility: user-only).
userstringNoFilter by a specific user (login ID) or ALL.
approvalStatusCodestringNoFilter by approval status code (e.g. A_NOTF, A_PEND, A_APPR).
limitnumberNoNumber of records to return (default 25, max 100).

sap_concur_get_report

ParameterTypeRequiredDescription
accessTokenstringYesSecret. SAP Concur OAuth bearer access token (visibility: user-only).
reportIdstringYesExpense report ID.
userstringNoLogin ID of the report owner (required when acting on behalf of another user).

sap_concur_list_users

ParameterTypeRequiredDescription
accessTokenstringYesSecret. SAP Concur OAuth bearer access token (visibility: user-only).
primaryEmailstringNoFilter users by primary email address.
limitnumberNoNumber of records to return (default 25, max 100).

Outputs

sap_concur_list_reports

  • data (json) — Array of expense report header objects (the Concur Items array).
  • metadata (json) — List metadata containing:
    • count (number) — Number of reports returned.
    • status (number) — HTTP status code returned by Concur.

sap_concur_get_report

  • data (json) — The expense report header object.
  • metadata (json) — Report identifiers containing:
    • id (string) — Report ID.
    • status (number) — HTTP status code returned by Concur.

sap_concur_list_users

  • data (json) — Array of user objects (the Concur Items array).
  • metadata (json) — List metadata containing:
    • count (number) — Number of users returned.
    • status (number) — HTTP status code returned by Concur.

YAML Example

sap_concur_1:
  type: sap_concur
  name: "SAP Concur"
  inputs:
    operation: "sap_concur_list_reports"
    user: "ALL"
    approvalStatusCode: "A_PEND"
    limit: 25
    accessToken: "{{SAP_CONCUR_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

  • Auth setup: These tools use a SAP Concur OAuth bearer access token, not a static API key. Obtain a token from SAP Concur's OAuth2 flow and supply it as accessToken (it is treated as a secret / password field). Store it as an environment variable and reference it with {{SAP_CONCUR_API_KEY}}.
  • Filtering reports: Use approvalStatusCode (e.g. A_PEND for pending, A_APPR for approved, A_NOTF for not submitted) together with user set to a login ID or ALL to scope sap_concur_list_reports. Both limit is capped at 100 and defaults to 25.
  • Acting on behalf of others: For sap_concur_get_report, pass the user (login ID of the report owner) when retrieving a report you do not own; otherwise the request is scoped to the token holder.
  • Chaining: List reports first, then feed a report's ID into sap_concur_get_report using {{sap_concur_1.data}} to drill into a specific report's details.