005 · API Integration / Flight
FitsAir
API Integration
Completed
2022
Integration
005
Year
2022
Duration
3 months
Team Size
2 engineers
Role
Integration Engineer
Real-time flight availability and booking via microservice integration
Overview
FitsAir integration adds Sri Lanka's FitsAir carrier to an existing OTA platform through a dedicated microservice. It handles availability polling, fare validation, booking, and webhook-based status updates — all wired into the platform's existing GDS-normalised schema.
Key Achievements
Plugged into existing OTA normalisation layer with zero changes to core booking flow
Exponential backoff retry logic handles FitsAir API instability gracefully
Webhook handler processes booking status updates asynchronously
Full test coverage on adapter layer with recorded API fixtures
Technical Challenges
01API instability
FitsAir's staging and production APIs had inconsistent response times and occasional downtime.
Solution →Implemented circuit breaker pattern with exponential backoff retries and a fallback that marks the carrier temporarily unavailable rather than failing the whole search.
02Schema mismatch
FitsAir's response format differed significantly from the platform's internal DTO.
Solution →Wrote a dedicated adapter that maps FitsAir-specific fields to the internal schema, keeping all carrier-specific logic contained in one file.
metrics.json
99.95%
Availability
<150ms
Latency
98.5%
Retry Success
12+
Routes Covered
Technology
Backend
Node.jsTypeScriptExpress
Integration
AxiosWebhook handlersRetry logic
Database
PostgreSQL
Architecture
MicroservicesAsync queuing
Development Timeline
Phase 01 · API Analysis
API docs reviewSandbox setupSchema mapping