CaptainBook connects with Globick to expand global distribution opportunities

Globick continues to expand its connectivity ecosystem with the integration of CaptainBook, a booking and management platform for tour and activity operators. This new API connection enables CaptainBook operators to reach a broader network of global travel distributors through Globick, opening up new opportunities to grow their sales.

CaptainBook is a booking engine designed for the AI era, helping tour and activity operators manage their daily operations while increasing sales. Its platform brings together operational management and AI-powered capabilities, enabling operators to manage their businesses more efficiently.

Through this new API integration, operators using CaptainBook can access Globick's global network of travel distributors, expanding their reach without the need to develop individual connections with each distributor.

At the same time, distributors connected to Globick can access additional tours and activities through their existing API integration, further expanding their product portfolio.

As Jerome Bajou, Co-Founder & CEO of CaptainBook, explains:

"Our goal at CaptainBook is to make it easier for tour and activity operators to manage their business while growing their sales. The integration with Globick expands the distribution opportunities available to our operators, connecting them with a broader network of global travel distributors through a single connection."

With CaptainBook joining its ecosystem, Globick continues to connect experience technology providers and travel distributors, making it easier to expand distribution through a single API.

One API. Endless connections. Plug and scale.


Who Will Win Agentic Booking? (The Answer May Be in the API)

There is an open debate in travel right now, also in tours and activities: When AI agents start booking experiences on behalf of travellers, who will get the agentic booking? The OTA or the operator selling direct?

Nobody knows yet. We don’t know how AI platforms will monetize it, which interfaces travellers will end up adopting, what role will pure agent providers take in customer support, or how quickly they will trust an agent to make a €300 booking without checking the details themselves.

But there is one part of this discussion that gets much less attention.

Can the product actually be bought by a machine?

At Globick, we spend our days with travel experience APIs. And if you look at the problem from that side, rather than from the consumer interface, something becomes quite obvious:

OTAs currently have an advantage.

Not necessarily because they have ad purchasing power, or stronger brands, but because their inventory is generally more ready to be understood, compared and booked by a machine.

Forget discoverability for a minute

Most conversations about agentic commerce focus on discovery.

AEO. Visibility. Reviews. Brand authority. Advertising models. Which sources LLMs will trust and which products they will recommend. All of that matters.

Actually, preliminary data recently shared by Propellic ahead of its upcoming 2026 study points in an interesting direction: AI directed 71% of participants to book directly with operators, while 68% already expressed a preference for booking direct.

That is an encouraging signal for operators. But it also highlights an important distinction: being discoverable by AI is not the same as being bookable by AI.

What happens when the agent doesn’t just recommend where to book, but has to understand the product, select the right option and complete the transaction itself?

That is the layer I’m interested in here.

But imagine discovery has already happened.

A traveller asks:

“Book a guided tour of the Sagrada Família in Spanish for two adults and my 10-year-old, tomorrow morning.”

The agent finds several possible products.

Now comes the difficult part.

It has to understand exactly what each product is, decide which one matches the request, check whether the right option is available, calculate the correct rates, collect whatever passenger information is required and complete the booking.

Without a human filling in the gaps.

And this is where the API matters.

When the buyer has no eyes

A website can hide a surprising amount of bad data.

A good photo helps explain the product. A well-designed page gives context. One FAQ fills in missing information. And ultimately there is a human reading everything and making sense of it.

An agent booking through an API doesn’t have that safety net. Yes, they may crawl the website to get product info and price details, but will it match with what the API is sending as structured data ?

It sees what the API returns. And if the information isn’t there, it has three options: skip the product, look somewhere else for the answer, or infer it.

None is particularly good if you are the operator trying to get the booking.

This changes what matters at the point of sale.

The design of the booking widget becomes irrelevant. The quality and structure of the data behind it become critical.

From what we see, there are three layers that determine whether an experience is really agent-ready.

1. Can the agent understand the product?

Let’s go back to the Sagrada Família example.

The agent needs to know whether the tour is guided. In which language. How long it lasts. Whether children are accepted and under which rate. What is included. Where the customer needs to go.

This sounds obvious. But it isn’t.

Every day at Globick we receive products directly from booking-system APIs with extremely limited content.

Every day at Globick we receive products straight from booking-system APIs that don’t carry that information. No localization. Sometimes no proper description, or just a single line. A title, a price, and little else.

What an agent receives: a title, a price, and not much more.

A human travel agent could call the operator. An AI agent trying to complete a transaction in seconds won’t. And even if it finds the missing information somewhere else, how do we know that information corresponds exactly to the product, option and rate it is about to book?

For agentic commerce, content completeness stops being a merchandising problem.

It becomes transactional infrastructure.

2. Can it understand what to book?

And then things get more complicated.

Many experience APIs expose options and rates that make perfect sense inside the operator’s own booking system but very little sense outside it.

Internal option names that only mean something to the operator.. Rate categories without age ranges. Similar products with unclear differences. Availability structures that require additional context to interpret correctly.

Which one should the agent book?

A human can often guess. A machine shouldn’t.

If the request is:

“Two adults and one child, English tour, with hotel pickup.”

the API needs to make it possible to identify exactly which option matches that request, which rates correspond to those travellers and whether that specific combination is available.

This requires clear options, explicit rate categories, age ranges and an unambiguous relationship between options, rates and availability.

In a human booking flow, bad structure creates friction. In an agentic flow, it can kill the transaction.

Or, potentially worse, create the wrong booking.

3. Can the API keep up?

Even if the product data is perfect, there is another challenge.

The transaction still has to work. 

Agents don’t behave like humans browsing a website. Instead, one user request can generate multiple calls across products, dates, options and rates within seconds.

That puts pressure on everything behind the API: Response times matter. Rate limits matter. Availability architecture matters.

If availability takes too long to return, the agent has alternatives.

If the API starts rejecting requests because its rate limiter was designed for human traffic, the agent has alternatives.

If cached availability says a slot exists but the booking request says otherwise, again, the agent has alternatives.

We have already measured how significant that last problem can be in our analysis of availability booking errors.

And then there is the very last step.

What information is actually required to book?

Full name for every passenger? Date of birth? Hotel pickup location? Passport details? Phone number?

If those booking questions are not exposed before the booking request, the agent doesn’t know it needs to ask the traveller.

The result is predictable: the booking reaches the last step and fails.

The last mile: everything the agent needs to know before it clicks “book”.

So why do OTAs start ahead?

This isn’t because operators or booking systems have done something wrong. Simply, most of these APIs were built for a different world, one wherehumans were still somewhere in the process and could compensate for imperfect data.

OTAs had a different problem.

If you want to sell thousands — or millions — of products from thousands of suppliers, you cannot depend on every supplier structuring information in exactly the same way.

So OTAs built the normalization layer themselves: Structured categories, standardized rates. Translated and enriched content, mapped booking questions, availability infrastructure capable of handling large volumes.

They didn’t build this for AI agents. They built it because aggregation doesn’t scale without structure. 

It just happens that agents need almost exactly the same thing.

But yet, this does not mean OTAs will win agentic booking.

Operators have important advantages too, particularly around direct commercial relationships, first-party information and control of their product. And the whole discovery layer is still very much up for grabs.

But if we isolate the transaction itself, what we see today is relatively clear:

OTA inventory tends to be more agent-ready than inventory coming directly from operator APIs.

That gap matters.

The API is becoming the storefront

For years, APIs were treated as plumbing, necessary infrastructure sitting somewhere behind the product.

Agentic commerce changes that: If the buyer is a machine, the API is effectively what the buyer sees.

  • Your product description is part of the storefront.
  • Your rate structure is part of the storefront.
  • Your booking questions are part of the storefront.
  • Your response time is part of the storefront.
  • And your availability accuracy is definitely part of the storefront.

Nobody knows yet whether OTAs, operators, AI platforms or some combination of them will capture most agentic bookings.

But one thing looks increasingly clear from the connectivity layer:

The winners will need inventory that machines can understand, evaluate and book without humans filling in the gaps.

The good news is that this is fixable.

Operators and booking systems can improve content structure, rate definitions, booking requirements, availability accuracy and API performance.

And those that do will be in a much better position regardless of which consumer interface ultimately wins. Because the next customer looking at your inventory might not be looking at it at all.

It will be an agent.

Related reading

1% versus 12% — The Hidden Cost of Availability Booking Errors

99% of Your Travel Experiences Catalogue Is Never Sold


LinkTwist Connects with Globick to Expand Operator Distribution

Globick continues to grow its connectivity ecosystem with a new integration that connects LinkTwist with Globick to expand operator distribution, giving tour and activity operators a new way to access global travel distribution through a single connection.

LinkTwist is an all-in-one technology platform for tour and activity operators, bringing bookings, availability, payments, operations and distribution into a single system. Its technology helps operators manage their business and connect with multiple sales channels from one place.

The integration connects LinkTwist directly with Globick, extending its distribution capabilities and giving its operators access to new global demand through a single API connection.

For LinkTwist operators, this means adding another route to distribution while continuing to manage their bookings, availability and operations from the LinkTwist platform. For travel distributors, it opens access to LinkTwist-connected tour and activity operators through Globick’s connectivity ecosystem.

“LinkTwist gives operators the tools to manage their bookings, availability and distribution in one place. Our integration with Globick extends their distribution capabilities, connecting our operators with new global demand through a scalable and efficient connectivity layer.”

— Anna-Maria Stathourou, Product Specialist at LinkTwist


Globick expands its connectivity ecosystem with BeMyGuest

Globick now connects you to BeMyGuest, the gateway to Asia-Pacific's best things to do. Through this integration, Globick customers gain access to a carefully curated portfolio of tens of thousands of tours, attractions, experiences, and event tickets.

BeMyGuest's core strength lies across Asia-Pacific's most sought-after destinations, including Singapore, Japan, Thailand, South Korea, Bali, Hong Kong, Malaysia, Vietnam, Taiwan, China, and the Middle East, while its rapidly expanding portfolio across Australia & New Zealand, Europe, and North America provides even greater global coverage through a single connection.

In addition to attractions and experiences, BeMyGuest has built a rapidly growing portfolio of sports and live events globally, including Formula 1, football, motorsports, and other major international events. This gives Globick clients access to a broader range of high-demand products through a single supply platform.

Built on deep, direct relationships with attractions and experience operators, BeMyGuest has curated one of Asia-Pacific's strongest portfolios of travel experiences. The company focuses on directly contracting the best things to do across the region's most popular destinations from iconic attractions and theme parks to premium tours and authentic local experiences. This quality-first approach delivers premium content, competitive B2B rates, and dependable inventory.

BeMyGuest's supply platform is trusted by leading travel brands around the world, powering the distribution of experiences through major OTAs, airlines, and travel companies, including Agoda, GetYourGuide, KKday, Klook, MyRealTrip, NOL Universe, Pelago, Singapore Airlines, Traveloka, Trip.com, Viator, amongst others.

Since 2012, BeMyGuest has been the preferred B2B API partner for many of the industry's leading travel brands as they built, expanded, and complemented their tours, attractions, and experiences offering, providing the connectivity and curated supply needed to scale their experiences business.


99% of your travel experiences catalogue is never  sold

99% of your travel experiences catalogue is never  sold

For years, the experiences industry has pursued the same objective: expanding supply. Every new supplier meant more products, more destinations and, ultimately, more choice for travellers. The underlying assumption has always been straightforward: the larger the catalogue, the greater the commercial opportunity. But what if we tell you that 99% of your travel experiences catalogue is never sold?

Rather than focusing on how many products are available, perhaps we should start asking how many products or categories actually generate business for our customers.

Looking at catalogue performance differently

To explore that question, we analysed the commercial activity of 20 resellers connected to Globick's network of supplier APIs between 1 January and 1 July 2026. Together, they made almost half a million experiences available for sale. During the same period, however, only 6,410 different products registered at least one booking.

In other words, just 1.35% of the available catalogue generated a booking. That is, 99% of the travel experiences catalogue is never sold.

That figure should not be interpreted as meaning that the remaining products have no value. In most cases, they never get to search results is prominent positions and therefore, never get in front of their potential customers. In other cases,  some may simply respond to very specific customer needs that OTAs are not realizing

Having inventory isn't the same as selling inventory

But the aggregated figures become even more interesting when looking at distributors individually.

99% of your travel experiences catalogue is never  sold
99% of your travel experiences catalogue is never  sold

For the purpose of this analysis, we focus on distributors managing broad and diverse catalogues. Within this group, even the strongest performer generated bookings for just 7% of the products available through Globick, while the median distributor generated bookings for less than 1% of its catalogue.

The implication goes beyond comparing one distributor with another. Even among companies managing broad and diverse catalogues, only a tiny fraction of the products available ever generate a booking. For the typical reseller in our analysis, more than 99% of the catalogue remained commercially inactive throughout the period studied.

Why does this happen?

The data itself doesn't provide the answer, and it is unlikely that there is a single explanation.

Catalogue performance may depend on many different factors. User experience, brand recognition, commercial model, market positioning, product specialisation, recommendation logic, customer behaviour, catalogue quality, personalisation and, increasingly, artificial intelligence may all play a role.

The important point is not identifying one definitive cause. It is recognising that having products available and having products that generate business are not necessarily the same thing.

That raises a question the industry rarely asks: How do we unlock the value of the catalogue that already exists, ensuring the right experiences can reach the right traveller?

Have we confused catalogue size with commercial value?

For years, the industry has naturally associated larger catalogues with greater commercial opportunity.

More products meant more choice >> More choice was expected to create more bookings.

But perhaps those assumptions deserve to be revisited.

Having 20,000, 50,000 or 100,000 products available does not automatically mean those products have a realistic opportunity to be discovered and booked.

Perhaps the next competitive advantage won't come simply from adding another thousand experiences. Perhaps it will come from increasing the commercial relevance of the catalogue that already exists, placing the right products to the right niche of customers. And perhaps AI won't simply improve discovery, but enable the industry to unlock value from inventory that, until now, has remained commercially invisible.

AI may change the question entirely

Today, much of the industry's attention is focused on AI Discovery.

How will travellers search? How will agentic commerce evolve? How will AI recommend experiences?

These are undoubtedly important questions. But perhaps the real transformation goes one step further.

Not simply better discovery. But better catalogue utilisation.

The evolution of the industry could perhaps be described in three stages:

  • Phase 1: More products.
  • Phase 2: Better discovery.
  • Phase 3: Better catalogue utilisation, potentially enabled by AI
99% of your travel experiences catalogue is never  sold
99% of your travel experiences catalogue is never  sold

The objective is no longer only to make more products available. Increasingly, it is about ensuring that more of those products have a genuine opportunity to reach the right traveller.

Discovery isn't the only challenge

Today, a large proportion of experience products never even have the opportunity to compete for a booking.

We don't yet know whether that's because travellers never search for them, because they receive little visibility, because demand simply isn't there, or because recommendation systems repeatedly surface the same products.

Artificial intelligence could fundamentally change this.

Not because it indexes products better, but because it understands travellers better.

  • Context.
  • Intent.
  • Preferences.
  • Previous behaviour.

Instead of recommending the most visible products, AI may increasingly recommend the most relevant ones.

If that happens, today's long tail could become tomorrow's hidden gems, not as a marketing slogan, but as a natural consequence of better personalisation.

Connectivity will also evolve

If the next competitive advantage lies in making more of today's catalogue commercially discoverable, connectivity also needs to evolve.

Simply connecting products will no longer be enough.

Connectivity is increasingly about preparing supply so AI can discover it, understand it and recommend it.

That requires much more than moving data between systems. It requires structured data, reliable availability, rich product descriptions, consistent taxonomies, meaningful attributes and high-quality content.

In other words, the value of connectivity will increasingly depend not only on how much inventory it connects, but on how well that inventory can be interpreted by intelligent systems.

The next question for the travel experiences industry

For years, the industry's challenge was relatively clear.

How do we make more experiences available?

The next decade may be defined by a different challenge.

How do we unlock the commercial value of the catalogue we already have? How do we ensure that more products have a genuine opportunity to reach the right traveller?

Perhaps AI will become the first technology capable of fundamentally changing that equation.

Not simply by improving discovery, but by making it commercially viable to recommend products that, until now, have remained virtually invisible.


New Integration: Resamare Joins the Globick Ecosystem

Globick continues to expand its connectivity ecosystem with a new integration with Resamare, a reservation and operations management platform for leisure and outdoor activity providers.

Resamare combines online booking, inventory management, reseller connectivity and day-to-day operational tools in a single system, helping operators streamline sales, distribution and customer management.

Through this integration, Globick connects directly to Resamare's platform and extends its capabilities into a broader global distribution ecosystem, making its network of outdoor activity operators accessible to global travel distributors through a single API connection.

Another step towards a travel experiences ecosystem where supply and distribution connect faster, scale easier and grow together.

“Resamare has built a strong operational platform for outdoor and leisure activity providers, with a clear focus on simplifying reservation management and distribution. By integrating with Globick, they extend these capabilities into a broader global distribution ecosystem, enabling more scalable connectivity between operators and international demand channels.”

— Xavi Boixeda, CEO at Globick


<1% versus 12% - The Hidden Cost of Availability Errors

What 45 days of real booking data reveal about connectivity infrastructure

Less than 1% versus 12%. That's the gap we see between the best and worst suppliers on our platform when it comes to one specific failure: a booking that gets rejected because the availability was no longer real. At Globick, connectivity is our whole business, so this is the kind of number we pay close attention to — and the kind worth explaining. Availability errors metric gets surprisingly little attention, despite shaping revenue, customer experience and operational load.

The industry loves to celebrate how many products are connected, how many suppliers are live, how many destinations can be sold. But what actually matters is simpler:

Can the booking be completed?

Over the last 45 days we analyzed booking performance across the Globick platform to understand one of the industry's most common and costly problems: availability-related booking failures. The results are a useful benchmark, and they point at a topic that deserves far more attention: the quality of connectivity infrastructure.

As always, supplier names and commercial details are anonymized. The goal isn't to criticize anyone. It's to share real operational data that can help the whole industry improve.

The invisible problem behind failed bookings

Every connectivity professional knows this scenario. A customer searches for an activity. Availability appears to exist. They go to checkout. The booking is sent to the supplier. The supplier rejects it, because the inventory is already gone.

To the customer, that feels like a broken promise. To the distributor, it's lost revenue. To the supplier, it's an avoidable support ticket and a dent in trust.

This is what we call an availability error. Unlike a technical outage or a configuration bug, it doesn't mean the booking system is broken. It means the availability shown to the customer no longer matched reality by the time they tried to book.

The system worked. The information was stale.

The benchmark: how often do availability errors happen?

Across the period we analyzed, availability errors hit roughly 1 in 22 booking attempts — a platform-wide rate of 4.63%.

That number alone is worth pausing on. One in twenty-two is not a rounding error. At scale, it's thousands of travelers who thought they had booked something that wasn't really there.

But the platform average hides the real story. The moment we split the data by how the inventory reaches us, the picture changes completely.

Not all connectivity models behave the same

At a high level, the industry runs on two models.

Direct contracting. The product is contracted directly with the operator who runs the activity. Whoever sells it is sourcing availability from the party that actually owns and controls the inventory, with no commercial layer in between.

Intermediated contracting. The product is sourced through one or more commercial intermediaries — aggregators, resellers, bedbanks — who sit between the operator and the seller. These intermediaries do a lot of valuable work: product aggregation, commercial contracting, supplier onboarding, customer service, content curation, distribution reach.

These services create enormous value. Honestly, much of the tours and activities ecosystem simply could not function without them — they are what let a small distributor sell a global catalogue, and what let a local operator reach markets it would never touch alone. The industry needs them.

But every extra layer is one more place where inventory information has to stay in sync. And that's where it gets interesting.

The difference is significant

Here is the availability error rate for each anonymized supplier, colored by model.

The pattern is not subtle. Intermediated suppliers run availability error rates from about 1% up to roughly 12%. Direct connections mostly sit under 2%.

Rolled up, the gap is stark.

Table 1 — Availability error rate by connectivity model

Availability failures were roughly 5.6 times higher when an intermediary layer sat between the distributor and the original inventory source.

Before anyone jumps to conclusions: this is not an argument against intermediaries. They solve real business problems. They accelerate distribution, they simplify contracting, they help suppliers reach markets they'd never access alone. The data isn't saying intermediaries are worse. It's saying something more precise: every additional commercial step the inventory passes through is another point where its availability can drift out of sync, and that demands a great connectivity infrastructure..

First, a quick word on caching

To understand why extra layers cause trouble, you need one simple concept: caching.

A cache is just a saved copy of information so you don't have to ask for it every single time. When a customer searches for an activity, the platform doesn't call the supplier live for every result — that would be slow and would bury the supplier under millions of requests. Instead it keeps a recent copy of "what's available" and shows that.

The catch is obvious once you say it out loud: a saved copy is only as good as the last time you updated it. The longer ago you refreshed, the more likely reality has moved on — a slot sold out, a price changed, a session got paused. That gap between the saved copy and reality is exactly where availability errors come from.

So every layer between the supplier and the customer typically keeps its own cache, refreshed on its own schedule. More layers means more copies, each potentially a little out of date. The problem usually isn't that anyone is doing a bad job — it's that keeping many copies in sync is genuinely hard.

Which brings us to the trade-off at the heart of every connectivity platform.

The cache paradox

Caching isn't optional — it's the only way to keep search fast and keep suppliers from being buried under requests. But it forces a three-way trade-off that no platform fully escapes.

Table 2 — The cache triangle

The catch is that pushing on one corner usually pulls on the others. More caching means faster searches and lower cost — but a higher risk of stale inventory. Less caching means better accuracy — but more API calls and higher operating cost.

Connectivity architecture is, at heart, the art of balancing these three forces. Nobody gets all three for free.

Four ways to cache availability

Most availability caches can be described along two dimensions: what you cache, and how often you refresh it. That gives four common approaches.

Dates only + fixed refresh is the simplest. You store available dates and refresh on a fixed clock — every hour, every six hours, every day. Easy to build, cheap to run, but a thinner customer experience and more live supplier requests.

Dates only + progressive refresh keeps the cache lightweight but makes the refresh dynamic: a slot tomorrow gets checked every few minutes, the next week every hour, anything beyond a month once a day. It puts resources where volatility actually is, and it's far more efficient than a flat clock.

Dates + sessions + prices + fixed refresh makes the choice of refresh frequency unforgiving. Refresh too rarely and all that detailed information goes stale fast, since sessions and prices change more often than dates do. Refresh too often and you flood the supplier with requests, losing the very efficiency the cache was meant to provide — at the extreme, a high-frequency refresh costs almost as much as having no cache at all. With a fixed clock there's no good answer: the same frequency is always too slow for near dates and wasteful for far ones.

Dates + sessions + prices + progressive refresh is the most sophisticated. You store a lot of commercial information and refresh it intelligently based on how volatile each date is. More engineering, more monitoring — but in our experience the best balance of performance and accuracy by a wide margin.

The last line of defense

No matter how advanced your cache gets, one principle should stay non-negotiable: validate availability in real time, immediately before creating the booking.

A cache is a prediction. A booking is a commitment. Those are not the same thing.

Even the best cache can't perfectly predict the moment inventory changes. Bookings land. Capacity shifts. Operators pause products or adjust manually. Real-time validation right before the booking is the safeguard that protects customers, suppliers, distributors and support teams from a failure that was entirely preventable. Skip it, and you're betting customer experience against cache accuracy — rarely a good trade. It's exactly how a supplier that could sit at 1% ends up closer to 12%.

What the industry should measure

We've gotten very good at measuring growth: connected suppliers, connected products, API calls, revenue, transactions. We pay far less attention to the metrics that decide whether a booking actually works:

  • Booking success rate
  • Availability error rate
  • Inventory synchronization latency
  • Availability freshness

These don't look as impressive on a slide as product counts. But a platform with fewer suppliers and higher booking reliability can deliver more real value than a giant catalogue that can't be trusted at checkout.

What we learned

The takeaway isn't that direct connectivity is superior, or that intermediaries should be avoided. Both are essential parts of a healthy distribution ecosystem, and intermediaries in particular create value that the industry genuinely could not replicate without them.

The real lesson is simpler: what separates a 1% supplier from a 12% one is investment in connectivity infrastructure. Cache architecture matters. Refresh strategy matters. Real-time validation matters most of all. None of these come for free — they take engineering time, monitoring, and a deliberate commitment to treat reliability as a feature, not an afterthought.

That investment is rarely visible from the outside, and it's easy to underestimate. We dug into exactly how much it costs to build and maintain connectivity properly in a rare, data-driven look at the true cost of API integrations — worth a read if you want to understand what's really behind a reliable booking flow.

The industry's next competitive advantage probably won't come from connecting more products. It'll come from making sure the products already connected can actually be booked.

Because connectivity isn't measured by how many activities appear on a screen. It's measured by how many bookings reach the supplier and stick. And increasingly, reliability is the most important feature of all.

This benchmark reflects aggregated, anonymized data observed across the Globick platform over a 45-day period. We share it because the tours and activities industry has too little public, real-world data on connectivity performance — and you can't improve what you can't see.


API integrations

A Rare, Data-Driven Look at the True Cost of API Integrations

In the tours & activities space, APIs are the backbone of how supply gets distributed. Which means that, sooner or later, every travel distributor ends up building its own connectivity layer. 

Some choose to do it internally. Others rely on external solutions. Both paths exist in the market.

What is less often discussed is the real cost structure behind building and operating those API integrations over time.

The Visible Costs of API Integrations

When teams evaluate a new API integration, the focus is usually on a few well-defined phases.

What is often overlooked is that each of these phases actually involves dozens of small tasks, iterations and dependencies.

1. Development

This is not just “building the integration”.

It includes:

  • Understanding and interpreting API documentation (often incomplete or inconsistent)
  • Mapping data models to your own system
  • Finding functionality gaps and remove blockers
  • Adapting existing architecture and previous integrations
  • Handling edge cases, errors and exceptions
  • Building, testing and validating end-to-end flows

In practice, this is a sequence of iterations, not a linear process.

2. Supplier Relationship

Beyond technical work, each integration requires continuous coordination with the provider:

  • Getting access to documentation and sandbox
  • Managing questions, clarifications and inconsistencies
  • Assessing the quality and completeness of testing data
  • Iterating based on feedback during certification

This is operational work that sits between product, tech and external teams.

3. Certification & Go-Live

Reaching production is not a single step:

  • Passing formal certification processes
  • Re-testing in production (sandbox data is often limited or unrealistic)
  • Fixing real-world issues post-launch

And importantly: Performance in production depends heavily on efficient design, coding quality, caching strategies and architectural decisions

4. Cloud & Infrastructure

This is also part of the visible cost, though often underestimated.

Each integration adds:

  • Processing load
  • Storage
  • Multiple environments (sandbox + production)

And in production, costs are not only volume-driven, they depend on how efficient your architecture is.

These are expected costs. They go into planning, budgeting, and timelines.

The Overlooked Costs of API Integrations

What is less visible at the beginning is what happens after integrations are live.

This is where APIs become ongoing operational systems.

1. Maintenance & Evolution

APIs change continuously: new versions, deprecated endpoints, and functional updates required by suppliers.

Let’s share some real data : based on our experience at Globick managing multiple integrations, this translates into an average of ~24 maintenance tasks per API, per year, and each of these tasks requires analysis, development, testing and deployment.

This is how that average looks in practice:

  • For restech A, we handled 38 maintenance tasks over 2 years
  • For restech B, 88 tasks over 3 years
  • For restech C, 126 tasks over 4 years
  • And for restech D, 64 tasks over 4 years

Different providers, same pattern: a continuous stream of work that doesn’t stop after go-live.

2. Monitoring & Control

APIs don’t fail loudly. They fail silently: availability mismatches, pricing inconsistencies, booking errors… Maintaining reliability requires continuous monitoring, debugging, fixing…

This is ongoing operational overhead.

3. Opportunity cost

Every hour spent building and maintaining integrations internally is an hour not invested in product, growth or commercial capabilities. This is rarely modeled but it’s one of the most relevant costs at scale.

4. The Cost of Getting It Wrong

There is another cost that is rarely quantified, but often far more impactful: the cost of a poorly built integration. APIs don’t just fail technically—they fail commercially. Inefficient caching strategies, slow response times or inconsistent availability can directly impact conversion rates. Even a small drop, such as a 2% decrease in conversion due to latency or inaccurate data, can translate into significant revenue loss at scale. Unlike infrastructure or development costs, this impact is not always visible in dashboards, but it accumulates silently over time. In many cases, the revenue lost due to suboptimal integrations can outweigh the cost of building them properly in the first place.

What Does This Actually Cost?

Let’s translate this into a simple, realistic scenario.

Where the numbers come from

We assume a company that already has a platform in place to manage integrations and a minimum experienced team composed of 1 developer and 1 product / key account profile, 2 people dedicated full time to the job. For this exercise, we’ll use a €60K as the total company cost per person per year, taking Spain as a reference point — a reasonable midpoint between higher-cost markets (such as the US) and lower-cost ones (such as eastern Europe).

We also assume the company plans to implement full-featured integrations.

For each API integration, we assume the following effort distribution:

Effort per API

Component Effort Description
Development ~6 weeks + 20% additional time (inefficiencies and project management)
Supplier coordination & sandbox certification ~30% of development time
Production go-live & certification ~20% of development time
Maintenance & evolution ~96 hours/year per API (24 tasks × 4h per task on average)
Monitoring & control ~10% of annual development cost
Cloud & infrastructure ~€400 per API/month (including sandbox + production environments)

Cost per API

Cost Component Year 1 (rounded €) Recurring  ( rounded € / year)
Development 10K€ —
Supplier coordination & sandbox certification 3K€ —
Production go-live & certification 2K€ —
Maintenance & evolution

(for a single API)

14K€ 14K€
Monitoring & control 1K€ 1K€
Cloud & infrastructure 5K€ 5K€
Total per API 35K€ 20K€

What This Looks Like at Scale

Once you scale this model, the numbers add up quickly.

A company managing 25 API integrations over a 5-year period is looking at a total cost of over 2,8M€

With 10 integrations, that still means around 1,2M€ over the same period.

Even with just 5 integrations, the total cost is already close to 600K€.

This is not an edge case.

This is what happens when API integrations become part of your core operations.

What Does This Mean in Time?

If we translate these costs into time, the distinction between building and running integrations becomes clear. For the initial phase, a single API integration typically takes around 8 to 10 weeks end-to-end when combining development, supplier coordination and go-live. For a team handling multiple integrations sequentially, this means roughly 1.5 to 2 integrations per quarter. At scale, building 10 integrations would take close to a full year of continuous work for a small dedicated team, while 25 integrations could extend to 2+ years. Once live, the dynamic changes completely: maintenance becomes an ongoing operational load. Each API requires around 12 working days per year (~96 hours), meaning that 10 integrations already consume 4–5 months of work annually, and 25 integrations require the equivalent of more than a full-time person dedicated exclusively to maintenance. In other words, building integrations is a finite effort—but running them is a permanent one.

“Will Standards and AI development Solve This?”

Partially.

Standards like OCTO or tools like Claude Code or other agentic developments can improve efficiency, especially in the early stages.

From all the chapters laid out before, development and maintenance would be the most benefited from standardization and/or agentic development.

Let’s assume:

  • ~50% reduction in development effort
  • ~25% reduction in maintenance effort

The overall impact is meaningful, but limited.

Across the full cost structure, this typically translates into ~15–20% total cost reduction.

Why?

Because a large part of the cost does not disappear:

  • Monitoring
  • Infrastructure
  • Supplier-driven changes
  • Impact assessment to the current platform
  • Ongoing operational work
  • and many others

In other words: Standardization and AI can improve how integrations are built, but they don’t fundamentally change the cost of running them over time

Final Thought

APIs are not a one-time project. They are an operational system that grows with your business.

And as the number of integrations increases:

  • Complexity compounds
  • Costs become structural
  • Speed slows down

The real cost is not in building the first API integrations. It’s in running them at scale.


Broadway Inbound Joins Globick to Scale Theatre Distribution Globally

Globick adds a new partner to its connectivity ecosystem: Broadway Inbound, a specialized ticketing platform focused on theatre experiences and trusted Broadway inventory for group buyers and travel professionals.

This integration enables direct connectivity between Broadway Inbound and Globick, allowing its portfolio of shows to be distributed globally through a single API connection — with stable availability and booking flows aligned with B2B distribution needs.

For travel distributors, this means incorporating Broadway experiences into their offering in a more streamlined and reliable way, especially within complex itineraries. For Broadway Inbound, it opens the door to broader international exposure and new distribution opportunities.

A further step in simplifying how specialized experiences are connected to global demand.

“Broadway Inbound brings a unique level of specialization in theatre distribution. By connecting it to Globick, we enable travel distributors to access this supply in a way that is operationally efficient, scalable and ready to be integrated into complex itineraries.”

— Xavi Boixeda, CEO at Globick


New Integration: bookingkit Expands Globick’s Attractions Supply

Globick continues to expand its connectivity ecosystem with a new integration with bookingkit, a leading booking and ticketing platform for attractions in Europe.

Through this integration, bookingkit connects directly to Globick’s integration hub, enabling its network of attractions to reach global travel distributors through a single API connection — with real-time availability and consistent booking flows.

For bookingkit operators, this means expanding into international sales channels without adding operational complexity. For distributors, it simplifies connectivity and provides access to structured, reliable attractions supply through a single connection.

Another step forward in building a more connected, scalable and efficient experiences distribution ecosystem.

“Our integration with Globick allows bookingkit-connected attractions to access a wide network of global travel distributors through a single connection. This significantly reduces integration effort while ensuring real-time synchronization and a reliable, scalable distribution setup.”

— Lars Krösen, Head of Connectivity at bookingkit