Introducing the Meet API: Our Group Travel Engine, Now for Developers

Ask any group of friends or coworkers scattered across different cities where they should meet up, and you'll watch the same thing happen every time: a long pause, a few guesses, and eventually somebody picks the city they personally want to visit. Nobody does the math, because the math is genuinely hard. The fairest meeting point for a group is rarely the geographic middle, flights from hub cities are often cheaper than flights from closer towns, and the person flying the farthest usually gets quietly overlooked. This is the first question every distributed group asks, and until now there was no good tool to answer it.

That's the question the Jettova Meet API answers, and today it's available to developers in early access. Send it everyone's home cities, and it returns destinations ranked by the whole group's total flight cost, travel time, or carbon, with a per-person breakdown for every option so you can see exactly who travels how far and pays how much. It's the same fairness engine that powers group trips inside Jettova, offered as a single endpoint any product can build on.

Here's why we built it as a product and not just a feature. Every other travel API on the market starts working after a decision has already been made. Flight search tools need an origin and a destination. Routing tools move one traveler from a known A to a known B. They're all excellent at the booking half of travel and completely silent on the deciding half, which is exactly where group plans stall. The Meet API fills that gap: it's group decision infrastructure, the part no one else productized.

We also made it do more than rank. Most groups don't start from a blank map; they start from a short list. So the API can score just the cities you're weighing against each other, say Austin versus Denver versus Chicago, and tell you which is fairest for your specific group. It can sort to minimize the single worst journey instead of the group total, the sort an HR team wants when the goal is that nobody suffers a sixteen hour trek. It can filter to warm destinations, to specific countries, to major business hubs with the airports and hotels a company event needs, or cap results so no one flies more than a set number of hours or spends more than a set amount per head. And when you pass travel dates, every ranked city comes back with prefilled booking links, so your users go from where should we meet to booked in a single step.

Who is this for? Any product where people gather from more than one place. Company offsite and retreat platforms. HR and remote-team tools. Event and conference software. Reunion, wedding, and community apps. Travel startups that would rather build their own thing than reinvent the fairness math from scratch. If your users have ever argued about where to meet, this endpoint settles it with numbers.

The Meet API is the first piece of Jettova's group travel technology we've opened to developers, and it won't be the last. Full itinerary generation, planning from a video link, and embeddable group planning rooms are on the roadmap, and the order we ship them will be shaped by the teams who build with us early. Early-access keys include a free monthly tier, and there's a full reference, example requests, and pricing on our developer page.

We've spent this whole journey obsessed with one problem: getting a group of humans to actually agree on a trip and go. The Meet API is us handing the hardest part of that problem, the deciding, to every developer who wants it. If you're building something where people come together from different places, we'd love to see what you make with it.