HUBie Technology
TravelHub API
One API. Multiple providers. Geocoding, routing, airports, hotels, and full door-to-door itineraries — orchestrated through a single, intelligent gateway.
HUBie Technology
TravelHub API
One API. Multiple providers. Geocoding, routing, airports, hotels, and full door-to-door itineraries — orchestrated through a single, intelligent gateway.
Why a Travel Gateway?
Every TIC audit involves travel — inspectors flying to factories, driving between sites, coordinating across time zones. But travel data is fragmented across dozens of providers, each with its own API, pricing model, and quirks. TravelHub eliminates that complexity with a single orchestration layer.
Provider Agility
Use Google for geocoding but HERE for routing — or swap them entirely. Per-request provider selection means zero client-side changes when your strategy evolves.
Failover & Resilience
If HERE goes down, Google picks up automatically. Circuit breakers, retries, and timeouts are built in via Resilience4j — your app never notices the difference.
Cost & Latency
Redis-based caching means repeated geocode and route lookups hit the cache instead of expensive third-party APIs. Faster responses, lower bills.
Unified Security
One API key, one access control layer. Scopes and provider allow-lists are enforced centrally — no scattered credentials across services.
API Surface
Nine endpoints covering the full travel data lifecycle — from address lookup to multi-modal itinerary planning.
/autocompleteAddress autocomplete with bias, country filters, and place types.
/geocodeForward geocode — turn a text query into structured coordinates.
/revgeocodeReverse geocode — turn lat/lng into a full address.
/routeGround routing for car, bike, pedestrian with duration and distance.
/transitPublic transit routing between two addresses.
/itineraryDoor-to-door multi-modal itinerary with preferences and constraints.
/airports/nearestFind nearest airports by radius, with hub and commercial filters.
/airports/matchMatch optimal airport pairs for origin–destination trips.
/hotels/aroundDiscover hotels near a location with pricing and distance.
The Vision: Intelligent Itineraries
TravelHub doesn't just look up addresses — it plans complete, multi-modal journeys. Optimise for speed, cost, CO₂, or accessibility. The itinerary engine combines all providers into one seamless trip.
How Provider Orchestration Works
Request Arrives
Your app sends a single request with an optional ProviderPolicy — which providers to use, in what order, and whether failover is enabled.
Orchestrator Decides
The orchestrator checks your policy, your API key scopes, and the provider allow-list. It picks the best provider for this request type.
Cache or Call
Redis is checked first. On a cache miss, the selected provider is called. Results are cached for future requests to save cost and time.
Failover if Needed
If the primary provider fails and failover is enabled, the next provider in the order list is tried automatically. Circuit breakers prevent cascading failures.
Under the Hood
The modules and infrastructure that power TravelHub.
Core Interfaces
Geocoder · RouterService · AirportServiceProvider-neutral contracts that every adapter must implement. Swap providers without touching business logic.
Provider Adapters
HERE.com · Google Maps · AeroDataBoxEach provider is an isolated adapter translating the unified schema into provider-specific API calls and back.
Cache & Resilience
Redis · Resilience4jTransparent caching layer with configurable TTLs. Circuit breakers, retries, and timeouts protect against provider outages.
API Layer
Spring Boot · OpenAPI 3.0RESTful controllers under /v1/geo with full Swagger documentation. API key authentication and rate limiting per provider.
Interested in TravelHub?
Whether you need a standalone geocoding service or a full itinerary engine — TravelHub adapts to your requirements. Let's talk about how it fits into your landscape.
Contact our expertssac-experts.com