Spend User v4 - Getting Started
Spend User Provisioning allows callers to provision or modify a user in the SAP Concur spend domain. This is an asynchronous downstream process from the User Provisioning v4 service. Currently, spend user data can be created, modified, and replaced with the POST, PATCH, and PUT provisioning operations. The retrieval of spend user data is supported through GET endpoints: One that can retrieve a filtered and paginated set of all spend users in a company, and another that can retrieve a specific spend user’s data using their unique identifier.
Limitations
This API is only available to partners who have been granted access. Access to this documentation does not provide access to the API.
Callers need to acquire the scope listed below in order to access the following extensions under spend domain.
Products and Editions
- Concur Expense Professional Edition
- Concur Expense Standard Edition
- Concur Invoice Professional Edition
- Concur Invoice Standard Edition
- Concur Request Professional Edition
- Concur Request Standard Edition
Scope Usage
| Name | Description | Endpoint |
|---|---|---|
spend.user.general.read |
View spend user information. | GET |
spend.user.general.writeonly |
Change spend user information. | POST / PATCH |
NOTE: In addition to the spend scopes, you will need the scopes listed in User Provisioning v4 in order to provision core user data.
Dependencies
Users must purchase Concur Expense in order to use the spend extensions to provision spend related data. Clients must use the User Provisioning v4 API to provision users in order to use this endpoint to retrieve user data.
Access Token Usage
This API currently only supports company level access tokens.
Additional Resources
See the following pages for further details.