What is the Itinerary API (Concur)

Have an app for travelers? Learn how to integrate with the Concur Platform using our Itinerary API. This brief video shows you how the API works and provides sample scenarios and key resources to start building.


Wearable World hackathon Round 1 Recap

With the upcoming Thanksgiving, we’re to witness once again one the busiest times of the year. Most airports will see increased traffic as travelers fly in and out of countries/cities.

The San Francisco International Airport, according to its facts page, has enplaned/deplaned roughly 45M passengers last 2013. It is also one of the few airports in the world that offer an API. It is through their API that they form a dialogue with developers – to help make SFO an enjoyable segment of travel for the 45M passing through.

To help achieve this goal, they partnered with Wearable World to run a series of developer challenges aimed at helping improve the overall airport experience from start to end. The recent installment of this challenge is a 2-part event, with Round 1 concluding just last November 18th at Say Media here in San Francisco. Just like the first installment of the WearableWorld developer challenge series, we were privelged to have had the opportunity to demonstrate the Concur API to developers, and work with them to craft ideas and solutions that serve the business traveler.

The event was kicked off by none other than Robert Scoble, blogger and author of Age of Context.

Each of the API partners then had a few minutes each to explain how developers can use their API towards the goal of the “Connected Airport”. That was followed shortly by a hearty lunch, then it was coding time!

The next day, we were back Say Media to help developers with their apps, and make sure they get submitted before 3pm to ChallengePost..

That was followed shortly by demos by the participants, who were given a few minutes to demonstrate their work in front of the judges. Judges were from WearableWorld, The San Francisco International Airport, American Airlines, Mastercard, Next-Gen Computing Wearables, and the San Francisco Mayor’s Office. Here’s a demo by ShuttleBeacon, that ended up winning the grand prize at the event! Their app helps passengers arriving at the airport to identify/encourage additional travel options, especially ones that use the existing public transport infrastructure, to get them to their destination. They’re using the Concur API to pull flight information (airport and departure/arrival times) to prepopulate items needed by the app.

You can check out all the other 5 teams that used/demonstrated a Concur API integration in our Twitter feed.

Overall, we had a blast at the WearableWorld event! Congratulations to the Wearable World team and the San Francisco International Airport Communications and Marketing team for putting together the hackathon, and getting Concur involved! And of course to ShuttleBeacon, for winning Round 1 of this event. We’ll see you again in Round 2!

Example of Concur Web flow (Trover)

You can find more details about the Web flow in the Concur’s developer page here.

  1. From Concur App Center, click “Connect”
    • 1
  2. Creation of new Trover account / or login to existing account.
    • 2
  3. Custom page to link Trover and Concur
    • 3
  4. Authorization page to allow Trover to access Concur user’s information
    • 4
  5. Custom connected page
    • 5
  6. Provide user with option to disconnect
    • 6

Where are all the Business Travel Apps?

Where are all the Business Travel Apps?
Sure, there are plenty of apps for leisure travelers.  But what about the lucrative market of business travelers?  Find out why business travel apps could be the opportunity your company needs.
Business Travelers vs. Leisure Traveler:
Business Traveler:
  • 5x trips/year (89% domestic)
  • Part of a frequent flier program (nearly 99% say this)
  • Spends avg. of $5,584/year
  • Avg. trip length is 4 days
  • Checks travel information on mobile devices (57% say this)

Leisure Traveler:

  • 1x trip/year
  • Part of a frequent flier program (nearly 34% say this)
  • Spends avg. of $1,372/year
  • Avg. trip length is 1-2 days
  • Checks travel information on mobile devices (38% say this)

The Business Travel Industry:

  • $1.12T market in 2013
  • 2/3 Business Travel / 1/3 Leisure Travel
  • 460M business trips in 1 year in U.S.
  • 10:1 return on investment for companies whose employees travel

Business Travel is an “Un-Apped” Market:

  • CFOs rank Travel and Expense the #1 candidate for mobile device experience, and strongly so
  • Most spend up to 4 hours per week planning and organizing for travel
  • Eight in ten travelers agree: mobile travel apps improve their business travel experience
  • 74% of business travelers rank business travel as very or extremely important to increased profits
  • It seems most apps are geared toward leisure travel rather than meeting the needs of traveling employees – Less than 10 of the top 50 iPhone apps are primarily focused on business travel

Put your app in front of 25M Business Travelers with Concur:

Concur Platform: Enables integration into highest use cases: Travel, Itinerary, Expense, E-Receipts

  • Global reach for 3rd-party apps: Provides T&E cloud services to 25M users from 20K businesses in 190 countries
  • Global co-marketing and Concur App Center: Joint marketing and the Concur App Center introduce new apps to 25M users and 20K businesses
  • REST-style APIs: Travel, Itinerary, Expense, E-Receipts, and Additional Services (TripIt, GDSX, conTgo)
  • Dev Tools: Sandbox, Technical Library, Sample Code, Web Test Guide, Certification

Why Concur?

  • High Transaction Volume: Concur processes 55M transactions worth $55B in Business T&E spend/year
  • 60% of Fortune 500 companies use Concur
  • 24% YoY Growth

Learn more about buildings apps with Concur: http://developer.concur.com/

Sources: frequentbusinesstraveler.com | biggestleaf.com | U.S. Travel Association | Global Business Travel Association | World Travel & Tourism Council | eMarketer | KRC Research | Concur | Gartner Inc.