Travel suppliers

Supply on Your Terms

Connect structured travel supply to Eridura's complete trip cards across flights, stays, activities, insurance, and destination services.

Supplier signal

Loading supplier data...

Reading Eridura's destination, hub, and spend datasets.

Detecting origin

Integration surfaces

Flight supply

Offers should normalize into clean price, route, segment, baggage, cabin, and timing details.

Stay supply

Hotel or property data should support nightly pricing, occupancy, cancellation terms, and deep links.

Add-on supply

Transfers, insurance, activities, passes, and destination services can become relevant after trip fit is known.

Integration priority

The best suppliers help Eridura answer one question quickly: can this complete trip work for this budget?

  • Availability and prices that can be checked programmatically
  • Stable destination identifiers such as IATA, city, country, coordinates, or hotel IDs
  • Booking handoff with attribution, commission, CPA, or commercial reporting

Useful supplier formats

Structured data wins because Eridura ranks and compares supply across the whole trip, not one product at a time.

  • API, XML, JSON, CSV, SFTP, affiliate feed, or structured deep-link catalog
  • Currency, taxes, fees, cancellation rules, baggage, room rules, or eligibility details
  • Sandbox credentials, rate limits, documentation, and support contact
1

Share the supply category

Flights, stays, activities, transfers, insurance, ancillaries, destination content, or mixed inventory.

2

Review the data contract

We confirm identifiers, price structure, availability, attribution, and how results should be normalized.

3

Test inside trip cards

Supplier inventory should improve budget fit, booking confidence, or destination usefulness for the traveler.

Connect travel supply to Eridura

Send your supplier type, API/feed method, markets covered, rate limits, and preferred commercial model.

platforms@eridura.com