Skip to content

Commit a347395

Browse files
[skip ci] Updates
1 parent f5a568c commit a347395

3 files changed

Lines changed: 11 additions & 15 deletions

File tree

feed.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55
<description>Concur docs provides comprehensive information on working with the Concur platform</description>
66
<link>https://preview.developer.concur.com/</link>
77
<atom:link href="https://preview.developer.concur.com/feed.xml" rel="self" type="application/rss+xml" />
8-
<pubDate>Wed, 03 Jun 2026 18:58:11 +0000</pubDate>
9-
<lastBuildDate>Wed, 03 Jun 2026 18:58:11 +0000</lastBuildDate>
8+
<pubDate>Thu, 11 Jun 2026 18:56:05 +0000</pubDate>
9+
<lastBuildDate>Thu, 11 Jun 2026 18:56:05 +0000</lastBuildDate>
1010
<generator>Jekyll v4.1.1</generator>
1111

1212
</channel>

solutions/app-center.html

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -220,26 +220,18 @@ <h3>
220220
Our partner ecosystem is critical to SAP Concur. We’re looking for innovative companies with compelling integration
221221
ideas to solve real business problems for the 60 million business travelers and 48 thousand enterprises worldwide
222222
already using SAP Concur. If your business is well established and you’re committed to develop, market, and support your
223-
integration, we’d like to talk with you about our App Center Partner Program (fees apply). Click the link below to send
224-
an email to our business development team.
223+
integration, we’d like to talk with you about our App Center Partner Program (fees apply).
224+
</p>
225+
<p>
226+
Interested in partnering with SAP Concur? To ensure your request is properly reviewed, please complete our <a href="https://forms.office.com/pages/responsepage.aspx?id=bGf3QlX0PEKC9twtmXka95yuiIfDq99Lki7VCvW-3cdUOE8xWUpFTDZJR0EwSTFZVDlLUFdWVDFQOSQlQCN0PWcu&route=shorturl">intake form</a>.
227+
Our team will evaluate your submission and reach out if there is an opportunity to move forward.
225228
</p>
226229
<p>
227230
Note: Please review the <a href="http://www.concur.com/appcenter">SAP Concur App Center</a> and the available API documentation to assess if the integration you have
228231
in mind is practical as we only pursue partnerships that are technically feasible via the available APIs and are
229232
compelling to a large number of SAP Concur clients and/or their users. Please know that we have many requests and we
230233
cannot respond to every inquiry.
231234
</p>
232-
<p>
233-
Your email should include:
234-
</p>
235-
<ul>
236-
<li>Brief description of your company (what you do, number of years in business, number of customers and employees).</li>
237-
<li>Description of the integration scenario/application that you are looking to offer via the App Center.</li>
238-
<li>Examples of joint customers who are requesting the integration and what problems they’re trying to solve.</li>
239-
</ul>
240-
<p>
241-
<a href="mailto:concur_bizdev@sap.com" class="btn is-rounded concur-blue"><i class="fas fa-envelope"></i> Email Us</a>
242-
</p>
243235
<!-- Travel Suppliers -->
244236
<h3>
245237
Travel Suppliers

tools-support/release-notes/api/2026-06-03.html

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -441,6 +441,10 @@ <h1 id="api-release-notes-june-2026">API Release Notes, June 2026</h1>
441441

442442
<h2 id="new-this-month">New This Month</h2>
443443

444+
<h3 id="deprecation-company-cards-transactions-v1-api">Deprecation: Company Cards Transactions v1 API</h3>
445+
446+
<p>Effective June 6, 2026, the Company Cards Transactions v1 API will be deprecated. This has been replaced by Cards v4 API. Decommission will follow.</p>
447+
444448
<h3 id="preview-trips-v5-api-with-configurable-trip-event-subscriptions">Preview: Trips v5 API with Configurable Trip Event Subscriptions</h3>
445449

446450
<p>The Trips v5 API will provide customers and partners with a scalable and performant way to retrieve trip data based on a configurable event-based subscription model. This API will support the divisional view construct for TMC partners, however the event subscriptions would need the filter configuration setup to the appropriate travel configurations. Partners will receive only the trip and booking details relevant to their use cases, giving them a cleaner, more focused data set that simplifies their integration and reduces unnecessary noise.</p>

0 commit comments

Comments
 (0)