Programmatically create and retrieve travel itineraries using the TripIt API v1
domain: tripit.github.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a TripIt developer application at tripit.com to obtain OAuth 1.0a credentials; TripIt uses OAuth 1.0a, not OAuth 2.0
Implement the OAuth 1.0a request-token and access-token flows to obtain a user-authorized token before making API calls on behalf of a traveler
POST a travel confirmation email or structured reservation XML to the create endpoint to add a new trip segment such as a flight, hotel, or car rental to the user's TripIt account
GET the trip list for a user to retrieve all active itineraries, then GET individual trip details to access segment-level data including confirmation numbers, dates, and provider names
Use the CRS (Common Reservation Standard) API variant when integrating from a booking system to push confirmed reservations directly without email parsing
Handle API rate limits gracefully; TripIt enforces per-application and per-user call limits that are not always explicitly surfaced in error messages
Known gotchas
TripIt uses OAuth 1.0a rather than the more common OAuth 2.0; libraries and frameworks that assume 2.0 will not work without modification, and signature generation errors are the most common integration failure
The TripIt API v1 documentation is hosted on GitHub at tripit.github.io and has not been substantially updated recently; some behaviors are better documented in the GitHub issues forum than in the formal docs
TripIt may parse confirmation emails automatically if the user has email-forwarding enabled; POSTing a reservation that TripIt already ingested via email can create duplicate segments — check for existing segments before creating
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?