TripIt third-party integrations are no longer working
As of August 29, 2026, at 12:31 UTC, TripIt is returning a 404 error when users attempt to connect their accounts to third-party services, including Tripsy.
This is unfortunate news for TripIt users who rely on integrations to access, sync, or move their own travel data between services.
So far, we haven’t found any public announcement from TripIt explaining the change. The only related information we could find is an older article on their support website:
Users attempting to connect TripIt with Tripsy will currently receive a 404 error instead of being able to authorize their account.
When did this start?
The first report we received came from a Tripsy customer on August 28 at 20:12 UTC, after they tried to sync their TripIt data with Tripsy and received a 404 error.
We’ve since confirmed that the TripIt authorization flow used by third-party integrations is no longer working.
What can we do now?
Unfortunately, there’s nothing we can change on the Tripsy side to restore this integration.
We’re trying to reach TripIt to better understand what happened and whether this is a temporary issue or a permanent change.
We hope TripIt restores access and continues allowing users to connect their accounts to other services and access their own travel data.
Update: September 15th, 2026
Whilst we haven't had any positive update from TripIt, we have been working behind the scenes with our amazing user community to find ways to get your TripIt data into Tripsy.
We've updated our guide with some details of how you can use Claude's Cowork feature to scrape the data via their Chrome extension.
We also have options for our PRO customers, if you can get your data from TripIt.
What about existing connections?
So far, existing TripIt connections appear to continue working normally. If you’ve already connected your TripIt account to Tripsy, your existing sync should remain active.
At the moment, the issue appears to affect new connections and authorizations. We’re continuing to monitor existing connections as well, and we’ll update this post if anything changes.
Your travel data should belong to you
At Tripsy, we have a simple principle: your travel data belongs to you.
Tripsy has offered a public API for several months, as well as providing an MCP server that lets users connect their Tripsy data to third-party apps, services, and AI tools. Both our API and MCP server are available to all our users, without the need to subscribe our PRO features.
We believe users should be able to access their own information, move it, build on top of it, and connect it to whichever services they choose.
Similarly, we've also made a full data export available within Tripsy, so if you just want to make your own backups you have the freedom to do so.
Our job as a platform is not to lock your data in. It’s to make sure you can use it however you want — today and in the future.
