Travel tech / API integration ·In production
Supplier Integrations
Connecting one booking platform to many third-party travel suppliers, and keeping bookings correct when those suppliers are slow, fail or change their answers.
- Role
- Engineer & lead
- Company
- NZitech
- Scope
- Multiple travel suppliers
The problem
A travel platform is only as reliable as the suppliers behind it. Each one has its own API, its own speed and its own way of failing.
What working with many suppliers involves
- API timeouts and slow responses
- Failures and retries
- Availability that changes between search and booking
- Pricing differences between suppliers
- Booking issues that have to be traced and resolved
- Concurrency, when many customers search and book at once
- Real-time status updates through webhooks
My part
I build and maintain these integrations, and coordinate with the suppliers when something goes wrong on their side.
Built with
- Laravel
- REST APIs
- Webhooks
- Redis
- Queues