For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
    • Knowledge Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
      • Concur Approvals Access Requirements
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • Authentication
  • Method
  • Process Walkthrough
Access RequirementsExpense Management Access

Concur Approvals Access Requirements

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Calendar Management Access

Next
Built with

Authentication

Use this document for instructions on how to get the access setup in place for the Moveworks Expense Approvals integration with Concur.

Docs for reference:

  1. https://developer.concur.com/api-reference/authentication/apidoc.html
  2. https://developer.concur.com/api-reference/expense/expense-report/v3.reports.html

Refresh token expiration:

For security Concur company refresh tokens expire every 6 months & the customer will have to provide Moveworks with the new Company Request Token every 6 months. Moveworks team will then use the new Request Token to generate another valid Refresh token for the next 6 months.

Method

Moveworks will be authenticating into your Concur system via the Company Request Token Method. This lets us generate a 1-time Company Request Token (valid for 24 hours) followed by refreshable access tokens which we’ll use to authenticate any interactions.

Pre-requisites: Customer must have access to the Web-Service tool in Concur.

Process Walkthrough

  1. Create a new OAuth 2.0 App with the required scopes.

    1. Navigate to OAuth 2.0 Application Management under Authentication Admin

    2. Client Create New App

    3. Fill in the following details:

      1. App Name: Moveworks Integration Application
      2. App Type: Client
      3. App Description: Moveworks uses this application to provide Concur expenses support into your native chat platform
      4. Allowed Grants: refresh_token, password, & client_credentials
      5. Allowed Scopes: openid, EXPRPT, expense.report.read, expense-report.readwrite, expense.report.workflowstatus.write, identity.user.core.read & identity.user.ids.read
    4. ❗Note down the generated Client ID & Client Secret

  2. Create a Company Request Token (which we’ll be using to authenticate into our application created above)

    1. Navigate to Company Request Token under Authentication Admin

    2. Now Paste the Client ID into the App ID & hit submit.

    3. ❗Note down the Company UUID & Company Request Token

Requirements: Please share the Client Id, Client Secret, Company UUID & Company Request Token with your Moveworks Customer Success team.