Architecture Case Study
Request & Information Flow
How customer criteria becomes a live supplier request and returns as a normalised website result.
Search flow
sequenceDiagram
participant C as Customer
participant W as Webflow
participant I as Integration layer
participant J as Holiday API
C->>W: Search criteria
W->>I: Normalised holiday search
I->>I: Validate and map request
I->>J: Authenticated live availability request
J-->>I: Availability, price and travel data
I->>I: Parse and normalise response
I-->>W: Website result model
W-->>C: Holiday results
Request information
The integration receives a customer search model containing the inputs required to perform a meaningful live availability request.
Examples include:
- origin/departure airport;
- destination;
- departure date;
- duration;
- adult occupancy;
- child ages;
- room requirements.
Response information
The external response can contain information such as:
- holiday price;
- accommodation;
- room/board;
- flight details;
- travel dates;
- destination information;
- onward supplier links or references.
The integration layer selects and normalises what the website actually needs.
Information ownership
The website owns the customer's current search state.
The supplier remains authoritative for live availability and price.
The integration service owns the translation contract between those two information models.
That distinction prevents transformed website data from being mistaken for an independent system of record.