A walkthrough on how to go from nothing to your first booking using the Duffel API. In order to follow this guide, you'll need to: \* [Sign up](https://app.duffel.com/join) for a Duffel Account (it takes about 1 minute!) \* Create a test token from the "Access Tokens" page in your [Dashboard](https://app.duffel.com/) and paste it in the `Authorization` section of the Postman Collection (**Don't forget to hit save afterwards**) ## Overview Multi-step search allows integrators to easily implement a flow that involves a traveller selecting one slice of their flight at a time as they build their whole flight itinerary. This enhances the search experience as the whole flow feels faster and intuitive. There will be significantly fewer offers returned overall, and at each stage. As an integrator with Duffel, this would simplify your job to process and display these offers and will aid the traveller in making a selection from the offers presented to them. ## How does the flow work? The entire flow takes 4 steps: 1. _**Outbound search**_: You pass the origin and destination `slices` and `passengers` and get back a list of partial offers for the outbound slice of your journey by [creating a partial offer request](https://duffel.com/docs/api/partial-offer-requests/create-partial-offer-request). A _**partial offer**_ is an offer that can’t be booked directly but can be passed to the next endpoint: show partial offer request. A partial offer contains only one slice, even if the search is for multiple slices. At the end of the flow (at fare selection), you pass in the partial offers for each of the slices in your journey to obtain a full offer that you can book. 2. _**Inbound search**_: You pass in the offer from the previous outbound search into the endpoint for the inbound search. This will be through the [partial offer request show endpoint](https://duffel.com/docs/api/partial-offer-requests/get-partial-offer-request-by-id). You’ll get back partial offers for the next slice of your journey. 3. _**Fare selection**_: You pass in the chosen partial offers obtained from the outbound and inbound search, to obtain a list of full offers. This will be through the [fares endpoint](https://duffel.com/docs/api/partial-offer-requests/get-partial-offer-request-fares-by-id). 4. _**Create order**_: Finally you make a booking by passing in the full offer ID obtained at fare selection while [creating an order](https://duffel.com/docs/api/orders/create-order). **NOTE:** By running the requests in the sequence mentioned above, you'll get most fields automatically pre-filled for you.
Versori has established itself as the third generation of Integration Platform as a Service (iPaaS). Versori builds custom integrations for its customers using an intuitive visual user interface.
Versori’s connector engine means there is no dependency on an existing library of apps, all you need to start is the documentation of the app or system you want to integrate to.
Drag and drop the Open API Spec into Versori's connector engine to create a new connector in minutes.
Build out visual integration workflows with powerful data tools on an intuitive canvas UI.
Deploy your automated workflow instantly and maintain your integrations with ease.
Is there something wrong with this spec? Let us know and Versori's engineering team will improve the quality of the spec based on your feedback.
Automatically match and transform data fields between systems with precision, reducing manual effort and errors.
Design integrations visually, test workflows instantly, and deploy seamlessly—accelerating your time to value.
Drag and drop API specifications to build custom integrations, unlocking endless connectivity with minimal setup.