You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: api-guides/e-receipts-enterprise-app-integration-guide.html
+27-26Lines changed: 27 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -631,7 +631,7 @@ <h3 id="sandboxes-and-accounts">Sandboxes and Accounts</h3>
631
631
632
632
<ul>
633
633
<li>You will have a sandbox on each of following SAP Concur data centers: US2, EU2.</li>
634
-
<li>Three initial test accounts on each of following SAP Concur data centers: US2, EU2. Additional accounts may be created. For further information, see <ahref="https://help.sap.com/docs/CONCUR_EXPENSE/85f3db6f3c5945fe8414a08fc5f9e3fc/bb4e99add95a497ab6fe4451cca1b39f.html">Manager Users</a>.</li>
634
+
<li>Three initial test accounts on each of following SAP Concur data centers: US2, EU2. Additional accounts may be created. For further information, see <ahref="https://help.sap.com/docs/CONCUR_EXPENSE/85f3db6f3c5945fe8414a08fc5f9e3fc/bb4e99add95a497ab6fe4451cca1b39f.html">Managing Users</a>.</li>
635
635
</ul>
636
636
637
637
<h3id="development-app">Development App</h3>
@@ -660,18 +660,21 @@ <h2 id="app-center-flow---connecting-from-sap-concur-app-center">App Center Flow
660
660
<p><ahref="https://developer.concur.com/api-reference/authentication/company-auth.html">Company Level Authentication</a> allows a company admin user to establish a connection from App Center. The admin user needs to login via their SAP Concur credentials to access the app in the App Center. In the development and testing phase, you would be provided with the app listing solely for the purpose of development and testing. This app listing will be accessed via a deep link. This deep link will be provided to you before you start development. The instructions to connect/authenticate via password grant are:</p>
661
661
662
662
<ol>
663
-
<li>
664
-
<p>A logged in user clicks the connect button on the app listing in the App Center and authorizes your app to post data. App Listing Example:</p>
663
+
<li>A logged in user clicks the connect button on the app listing in the App Center and authorizes your app to post data.</li>
664
+
</ol>
665
665
666
-
<p><imgsrc="/assets/img/api-guides/e-receipts-enterprise/step-1.png" alt="Example of App Center Listing Page" /></p>
667
-
</li>
666
+
<p><strong>Example of App Listing:</strong></p>
667
+
668
+
<p><imgsrc="/assets/img/api-guides/e-receipts-enterprise/step-1.png" alt="Example of App Center Listing Page" /></p>
669
+
670
+
<ol>
668
671
<li>
669
672
<p>After the admin user clicks the “Connect” button, the admin user will see a prompt with the terms & conditions. Admin user agrees to the terms and conditions and clicks the “I Agree” button.</p>
670
673
671
674
<p><imgsrc="/assets/img/api-guides/e-receipts-enterprise/step-2.png" alt="Screenshot of App Listing Terms and Conditions" /></p>
672
675
</li>
673
676
<li>
674
-
<p>The authorization service will redirect the admin user to your app’s <ahref="https://developer.concur.com/manage-apps/go-market-docs/app-center-partner-marketing-toolkit.html#landing-pages">landing page</a>. Please follow the <ahref="https://developer.concur.com/manage-apps/go-market-docs/app-center-ux-guidelines-consumer.html">App Center Design Guidelines</a> to create a web page that listens for an HTTP GET request. The<ahref="https://developer.concur.com/manage-apps/go-market-docs/app-center-ux-guidelines-consumer.html#guideline-checklist">Guideline Checklist</a> provides a list of required and recommended components of your landing page design. Please make sure all the required options are checked before scheduling the certification walkthrough.</p>
677
+
<p>The authorization service will redirect the admin user to your app’s <ahref="https://developer.concur.com/manage-apps/go-market-docs/app-center-partner-marketing-toolkit.html#landing-pages">landing page</a>. Please follow the <ahref="https://developer.concur.com/manage-apps/go-market-docs/app-center-ux-guidelines-consumer.html">App Center Design Guidelines</a> to create a web page that listens for an HTTP GET request. The<ahref="https://developer.concur.com/manage-apps/go-market-docs/app-center-ux-guidelines-consumer.html#guideline-checklist">Guideline Checklist</a> provides a list of required and recommended components of your landing page design. Please make sure all the required options are checked before scheduling the certification walkthrough.</p>
675
678
</li>
676
679
<li>
677
680
<p>Your landing page should allow an admin user to log in/authenticate.</p>
@@ -696,7 +699,7 @@ <h2 id="app-center-flow---connecting-from-sap-concur-app-center">App Center Flow
696
699
<li>Please refer <ahref="https://developer.concur.com/api-reference/authentication/apidoc.html#password-grant-">password grant</a> for the post body description.</li>
697
700
</ul>
698
701
699
-
<p><strong>Example : Password Grant</strong></p>
702
+
<p><strong>Example of Password Grant</strong></p>
700
703
701
704
<p><strong>Request</strong></p>
702
705
@@ -773,12 +776,7 @@ <h3 id="refreshing-a-token">Refreshing a Token</h3>
773
776
</ul>
774
777
775
778
<ol>
776
-
<li>
777
-
<p>If a company’s integration is idle for six months the <codeclass="language-plaintext highlighter-rouge">refresh_token</code> will expire and the company’s partner account and SAP Concur account will be de-linked. To prevent this from happening, build a scheduled job that scans your database for expiration dates and refreshes tokens X days prior to expiration. Refer <ahref="https://developer.concur.com/api-reference/authentication/apidoc.html#refreshing-a-token-">Refreshing a Token</a> API for the post body description and example.</p>
778
-
</li>
779
-
<li>
780
-
<p>Watch this section of the video <ahref="https://youtu.be/ikCU1235QJA?t=300">SAP Concur Integration 3 of 5 ; API Tokens</a>, which explains the difference between refresh and access tokens and how to refresh the access token.</p>
781
-
</li>
779
+
<li>If a company’s integration is idle for six months the <codeclass="language-plaintext highlighter-rouge">refresh_token</code> will expire and the company’s partner account and SAP Concur account will be de-linked. To prevent this from happening, build a scheduled job that scans your database for expiration dates and refreshes tokens X days prior to expiration. Refer <ahref="https://developer.concur.com/api-reference/authentication/apidoc.html#refreshing-a-token-">Refreshing a Token</a> API for the post body description and example.</li>
782
780
</ol>
783
781
784
782
<h2id="roster-sync">Roster Sync</h2>
@@ -813,11 +811,12 @@ <h3 id="getting-all-active-users">Getting All Active Users</h3>
@@ -1190,11 +1189,11 @@ <h3 id="get-the-employee-data-using-identity-v41">GET the employee data using Id
1190
1189
1191
1190
<h2id="posting-ereceipts">Posting eReceipts</h2>
1192
1191
1193
-
<p>For information on getting started with R<ahref="https://developer.concur.com/api-reference/receipts/get-started.html">eceipts v4</a>.</p>
1192
+
<p>For information on getting started with <ahref="https://developer.concur.com/api-reference/receipts/get-started.html">Receipts v4</a>.</p>
1194
1193
1195
1194
<ul>
1196
1195
<li>You should select General eReceipt type or Grand Transportation eReceipt type from the <ahref="https://developer.concur.com/api-reference/receipts/supported-receipt-types.html">Supported Receipt type</a> list and retrieve the list <ahref="https://developer.concur.com/api-reference/receipts/get-started.html">schemas</a> for the selected receipt types.</li>
1197
-
<li>To ensure that you are using the correct endpoint URLs, the safest practice is to check the service index before every request. <ahref="https://developer.concur.com/api-reference/receipts/endpoints.html#endpoint-service-index">Get service Index</a>.</li>
1196
+
<li>To ensure that you are using the correct endpoint URLs, the safest practice is to check the service index before every request. <ahref="https://developer.concur.com/api-reference/receipts/endpoints.html#endpoint-service-index">Get Service Index</a>.</li>
1198
1197
<li>We generate a standard receipt if you do not provide a receipt image.</li>
1199
1198
<li>We can display your app logo in standard generated receipts (size 100x100 px). Please send your company logo image file (.png) to <ahref="mailto:[email protected]">[email protected]</a>.</li>
1200
1199
<li>If your app currently generates a receipt image in .png, .jpg, .tif, .pdf, or other image file, you can include it in your post. Follow the requirement of <ahref="https://developer.concur.com/api-reference/receipts/endpoints.html#definitions-of-resources">supported image formats</a> if you are posting the eReceipts with images.</li>
@@ -1345,7 +1344,7 @@ <h3 id="post-a-ground-transportation-ereceipt">Post a Ground Transportation eRec
1345
1344
<li>The <ahref="https://developer.concur.com/api-reference/receipts/supported-receipt-types.html#ground-transport-receipt">Ground Transportation</a> eReceipt Schema includes all forms of non-aerial transportation and all <ahref="https://developer.concur.com/api-reference/receipts/supported-receipt-types.html#receipt-core-definitions">Receipt Core Definition</a>.</li>
1346
1345
</ol>
1347
1346
1348
-
<p>Refer to the <ahref="https://developer.concur.com/api-reference/receipts/sample-receipts.html#ground-transport">Grand Transportation eReceipt</a> POST example.</p>
1347
+
<p>Refer to the <ahref="https://developer.concur.com/api-reference/receipts/sample-receipts.html#ground-transport">Ground Transportation eReceipt</a> POST example.</p>
1349
1348
1350
1349
<h4id="response-codes">Response Codes</h4>
1351
1350
@@ -1364,7 +1363,7 @@ <h4 id="creating-a-quick-expense">Creating a Quick Expense</h4>
1364
1363
<li>Post the quick expense using the <ahref="https://developer.concur.com/api-reference/expense/quick-expense/v4.quick-expense.html#create-a-quick-expense-">Quick Expense</a> endpoint.</li>
1365
1364
<li>You should store the concur-correlationid from the response headers and the quickExpenseIdUri from the response body. This will facilitate support efforts in case of a missing quick expense from user’s SAP Concur account.</li>
1366
1365
<li>The <ahref="https://developer.concur.com/api-reference/expense/quick-expense/v4.quick-expense.html#schema-">Quick Expense Schema</a> includes required fields of expenseTypeId, transactionAmount, and transactionDate.</li>
1367
-
<li>The supported <codeclass="language-plaintext highlighter-rouge">expenseTypeId</code> value can be retrieved from <ahref="https://developer.concur.com/api-reference/expense/expense-report/expense-group-configurations.html">Expense Group Configurations v3.0</a>. The frequently used <codeclass="language-plaintext highlighter-rouge">expenseTypeId</code> values are listed below:</li>
1366
+
<li>The supported <codeclass="language-plaintext highlighter-rouge">expenseTypeId</code> value can be retrieved from <ahref="https://hub.sap.com/api/ConcurExpenseExpenseConfigurationService/overview">Expense Configuration Service</a>. The frequently used <codeclass="language-plaintext highlighter-rouge">expenseTypeId</code> values are listed below:</li>
<p>This response is also for cases where the JWT does not include the scope required to fulfill the request.</p>
1638
1637
1639
-
<p><strong>Error 404</strong>
1640
-
The receipt(s) you requested could not be found. Check that the receipt and/or user ID are correct.</p>
1638
+
<p><strong>Error 404</strong></p>
1639
+
1640
+
<p>The receipt(s) you requested could not be found. Check that the receipt and/or user ID are correct.</p>
1641
+
1642
+
<p><strong>Error 500/503</strong></p>
1641
1643
1642
-
<p><strong>Error 500/503</strong>
1643
-
Error 500 is an internal server error. If you receive an error 500 while posting an eReceipt, you should retry the API at least 3 times. If you still encounter an error 500 after retrying, please log a support ticket.</p>
1644
+
<p>Error 500 is an internal server error. If you receive an error 500 while posting an eReceipt, you should retry the API at least 3 times. If you still encounter an error 500 after retrying, please log a support ticket.</p>
1644
1645
1645
1646
<p><strong>Error Logging</strong></p>
1646
1647
@@ -1656,7 +1657,7 @@ <h2 id="faq">FAQ</h2>
1656
1657
1657
1658
<p>There will be a one-week certification time window per month. You should send your certification walkthrough request to <ahref="mailto:[email protected]">[email protected]</a> one month before the certification date you would like schedule. We will reply with a meeting invitation within 5 business days.</p>
1658
1659
1659
-
<p>Please find your certification date time based on the <ahref="https://developer.concur.com/api-guides/user-app-certification-calender.pdf">certification calendar</a>.</p>
1660
+
<p>Please find your certification date time based on the <ahref="https://developer.concur.com/api-guides/app-certification-calendar.pdf">certification calendar</a>.</p>
1660
1661
1661
1662
<p><strong>How do I log a support case?</strong></p>
Copy file name to clipboardExpand all lines: tools-support/release-notes/api/2026-03-03.html
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -491,6 +491,8 @@ <h2 id="ongoing">Ongoing</h2>
491
491
492
492
<h3id="important-upcoming-shutdown-of-request-v1-v3-and-v31">Important! Upcoming Shutdown of Request V1, V3, and V3.1</h3>
493
493
494
+
<p>Effective Date: August 5, 2026</p>
495
+
494
496
<p>As previously announced, the Concur Request APIs v1.0, v3.0, and v3.1 have been decommissioned. These versions will be retired and no longer accessible as of August 5, 2026. Customers currently using these versions must migrate to the successor API, Request API V4, to ensure uninterrupted functionality. Please reach out to your Concur representative for more information.</p>
495
497
496
498
<h3id="preview-removal-of-concurprofile-and-concurapp-fields-from-access-tokensjwts">Preview: Removal of concur.profile and concur.app Fields from Access Tokens(JWTs)</h3>
0 commit comments