Validation & Outcomes

Validation approach

The integration design was validated against the live API interaction required for the customer search flow.

Validation established:

• authenticated connectivity;
• construction of representative live availability requests;
• successful holiday search responses;
• retrieval of pricing and travel/accommodation information;
• transformation into a frontend-friendly result model;
• the separation between website presentation and supplier-specific integration concerns.

The design was also reviewed in the context of the wider website model, particularly the difference between live search and catalogue-backed discovery.

Findings

The key finding was architectural rather than protocol-specific:

live availability should remain a live integration concern.

Trying to hide the supplier behind the same assumptions used for synchronised catalogue data would weaken information accuracy and obscure the external dependency.

The backend boundary provides a cleaner place to own authentication, transformation, network constraints and failure handling.

Outcome

The resulting architecture gives the website a stable way to consume live holiday search without becoming coupled to supplier-specific transport or authentication.

It also keeps the system boundary controlled:

• Webflow owns the customer experience;
• the integration service owns the supplier contract;
• the supplier owns live availability and price;
• booking remains outside the website's initial responsibility.

That separation reduces unnecessary complexity while leaving a clear path for the capability to evolve if the customer journey expands later.