Reise-API · v1
Bauen Sie auf der ganzen Reise auf
Eine Integration, zwei Produkte: die Flug-API (Tarifkalender, Suche, Bepreisung, Zusatzleistungen, Auftrag, Ticket, Stornierung) und die Hotel-API (Suche nach Stadt oder Hotelcodes, Zimmer, Ratenprüfung, Buchung, Stornierung), dazu statische Inhalte. Sauberes JSON über HTTPS, signierte Anfragen, eine Basis-URL für Sandbox und Produktion.
Basis-URL
https://api.dubaitrip.com/v1Eine URL für Sandbox und Produktion – der Schlüssel entscheidet: dt_sbx_-Schlüssel erreichen die Testsysteme unserer Anbieter, dt_live_-Schlüssel das Live-Angebot.
Leitfäden
- SchnellstartVon der Registrierung bis zum gebuchten Flug in der Sandbox, in fünf Schritten.
- AuthentifizierungZwei Wege zur Authentifizierung, beide an Ihre Schlüssel-ID gebunden: signierte Anfragen (empfohlen) oder Bearer-Tokens per OAuth 2 Client Credentials.
- Umgebungen, Limits und VersionierungEine Basis-URL für Sandbox und Produktion; der Schlüssel, mit dem Sie signieren, wählt die Umgebung.
- FehlerJeder Fehler ist ein Problemdokument nach RFC 7807 mit einem stabilen, maschinenlesbaren Code.
- Flug-APITarifkalender, Suche über 900+ Fluggesellschaften, ein Angebot bepreisen, Zusatzleistungen hinzufügen, einen Auftrag erstellen, Tickets ausstellen, Erstattungen kalkulieren und abwickeln.
- Hotel-APIDurchsuchen Sie 1.5M+ Unterkünfte nach Städtecode (im IATA-Stil, z. B. DXB) oder nach den Hotelcodes, die Sie aus unserem Katalog speichern, lesen Sie Raten auf Zimmerebene mit Verpflegungsart und Stornobedingungen, validieren und buchen Sie, und stornieren Sie gemäß den Bedingungen.
- Statische InhalteReferenzabfragen zum Aufbau einer Suchoberfläche und zum Speichern unseres Hotelkatalogs nach Stadt: Flughäfen, Fluggesellschaften, Städte und Hotels.
- ÄnderungsprotokollJede Änderung an der Reise-API, die neueste zuerst.
Endpunkte
Authentifizierung
Konto
Flüge
- get
/v1/flights/price-calendarCheapest fare per day for a route over a date window, from our price cache — instant and never a live supplier call. Draw a fare calendar before searching. Omit the return window for one-way prices. - post
/v1/flights/searchSearch flights. Returns a session to poll, or the complete result when `wait` is true. - get
/v1/flights/search/{searchId}Read the next page of a running search. `status` becomes `complete` when every supplier answered. - post
/v1/flights/offers/{offerId}/priceRe-price an offer right before booking. `priceChanged` tells you the total moved. - get
/v1/flights/offers/{offerId}/fare-rulesFare rules and conditions of an offer. - get
/v1/flights/offers/{offerId}/ancillariesChargeable extras available for an offer — today extra checked-baggage allowances, priced by the airline per passenger. Add them to the order via `ancillaries[]` on POST /v1/flights/orders. - post
/v1/flights/ordersCreate an order (hold) from an offer. Requires an `Idempotency-Key` header. - get
/v1/flights/orders/{orderId}Read an order: status, time limit, tickets. - post
/v1/flights/orders/{orderId}/issueIssue the tickets of a held order (charges your deposit balance). - get
/v1/flights/orders/{orderId}/refund-quoteWhat a cancellation would refund, before you commit. - post
/v1/flights/orders/{orderId}/cancelCancel: a held order is released; a ticketed order is voided inside the void window, else refunded. - get
/v1/flights/scheduleTimetable for a route on one day: which flights operate, with local times and equipment — no fares. Query: `origin`, `destination` (IATA), `date` (yyyy-MM-dd). - post
/v1/flights/orders/{orderId}/exchange/searchExchange step 1: search replacement itineraries for a ticketed order. Offers come back in the search shape and expire the same way. - post
/v1/flights/orders/{orderId}/exchange/quoteExchange step 2: what exchanging the listed tickets onto an offer would cost. No side effects. - post
/v1/flights/orders/{orderId}/exchangeExchange step 3: re-issue the listed tickets onto the offer (charges your deposit balance). Requires an `Idempotency-Key` header.
Hotels
- post
/v1/hotels/searchSearch hotels by city code (IATA-style, e.g. DXB — see /v1/content/cities), by hotel codes from your stored catalogue, or by a geo circle. Returns a session to poll, or the complete result when `wait` is true. - get
/v1/hotels/search/{searchId}Read the next page of a running search. Pass the same dates and room count as the search so rate keys stay bookable. - get
/v1/hotels/{hotelCode}/roomsRoom types of a hotel. Pass any `rateKey` from the same search so the right supplier answers. - post
/v1/hotels/rates/{rateKey}/checkPre-book check: confirms the rate is still bookable and its price. - post
/v1/hotels/bookingsBook a rate. Requires an `Idempotency-Key` header. - get
/v1/hotels/bookings/{bookingId}Read a booking (voucher). - get
/v1/hotels/bookings/{bookingId}/cancellation-quoteWhat a cancellation would refund, before you commit. - post
/v1/hotels/bookings/{bookingId}/cancelCancel a booking under its cancellation policy.
Inhalte
- get
/v1/content/airportsAirports (IATA), optionally filtered by a free-text term or a country. - get
/v1/content/citiesCities usable as a hotel search destination, optionally filtered by term or country. - get
/v1/content/airlinesAirlines (IATA two-letter codes). - get
/v1/content/hotelsLook up hotels by city and/or name — a lookup, not a catalogue export: a cityCode or a name of 3+ characters is required, 50 per page, 20 pages per query. Store the codes you need: availability is searched by `cityCode` or `hotelCodes`.