> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/expensemanagement/sapconcur.md).

# SAP Concur

SAP Concur uses the OAuth authentication standard. To authenticate using OAuth, you will need to create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties.&#x20;

Set the following connection properties and follow the steps below to call stored procedures to obtain the access token.

* OAuthClientId: Set this to the Key in your app settings.
* OAuthClientSecret: Set this to the Secret in your app settings.
* CallbackUrl: set to <http://localhost:3333>

When you test the connection, the provider gets OAuthAccessToken  and stores it in the OAuthSettings Location

To automatically refresh the token when it expires, set InitiateOAuth to REFRESH.

#### Important connection property: LoginId

&#x20;Login ID of the user. Can be used if the user account associated with the OAuth 2.0 access token has a Concur account with one of these roles: Web Services Administrator for Professional or Can Administer for Standard. Setting the Login ID to "ALL" will retrieve information for all accounts at the expense of certain tables that do not support this argument.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/expensemanagement/sapconcur.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
