Capability sheet
Amadeus and Dojo360
What the Amadeus connector can read and write, how it authenticates, and the limits to plan around.
- Status
- Partner accessDocs reviewed · Last reviewed 2026-10-20
- Categories
- Travel
- Industries
- Travel & tourism, Hotels, restaurants & hospitality groups
- Regions
- GCC, India, Singapore, Malaysia, US, UK, EU & ANZ
- API and auth
- Mixed API · OAuth 2.0
- Dojo360 can pull
- Availability
- Offers
- Bookings
- Dojo360 can push
- Bookings
- Changes
- Cancellations
- Webhooks
- No. Changes are picked up on a schedule.
- Sandbox
- Available
- Key limits
- Booking and ticketing require commercial agreements with the distribution provider.
- No webhooks; changes are picked up on a scheduled sync.
- Access requirements
- Amadeus Enterprise agreement for production booking.
Amadeus is a trademark of its owner and is used here for identification only. See third-party trademarks.
Stop running six islands
Ready to run it as one operation?
Start with a fixed-price Blueprint. We map every system you run, where work is done twice, and what your Dojo connects first.
Works with the systems you already run