Everything is built and waiting. The moment JTA provides API credentials, their live inventory appears alongside Jet2, Travelpack and JTA and Travelpack in every search — automatically.
Email sent to JTA — Lisa Scott responded within 24 hours
JTA uses /hotel_results with IATA airport codes — pre-fill links already live on site
Full adapter in place — mock data live now, switches to real feed the moment credentials arrive
Awaiting JTA_API_URL and JTA_API_KEY from Lisa — one paste into settings and we go live
Once we see JTA's JSON schema, map their fields to our normalised format (1-2 hours work)
JTA results appear alongside Jet2, Travelpack and JTA & Travelpack in every search — no customer action needed
🇦🇬 Antigua
🇦🇪 Dubai
🇲🇻 Maldives
🇧🇧 Barbados
🇲🇺 Mauritius
🇱🇨 St Lucia
"Do you offer an XML or REST API feed for agent integrations?"
Confirms whether we can pull live results directly
"Can customers book through the feed, or does it link out to your site?"
Determines whether bookings stay on FckItBookIt or redirect
"What commission structure applies to API bookings?"
Important for the business model
"Do I need to be ABTA/ATOL registered to access the feed?"
Compliance requirement to be aware of
"Is there a setup fee or monthly cost for API access?"
Budget planning
src/server/suppliers/jta-adapter.tsFull adapter with mock data, health check, and live fetch stub
registry.tsJTA registered alongside Jet2, Travelpack and JTA, Travelpack — searched in parallel
GET /api/searchAlready returns JTA results — try searching Antigua or Dubai
buildJTAUrl()100+ destination → IATA mappings, pre-fills JTA search form
/resultsJTA Holidays button in Search All Suppliers dropdown
JTA_API_URL + JTA_API_KEYAdd two secrets → adapter automatically switches to live feed
Questions before Monday?