# API Specification Enhancements

<table><thead><tr><th width="150">Date of Change</th><th>ZAPI Call </th><th>Description</th></tr></thead><tbody><tr><td>May 2, 2018</td><td></td><td>Addition of real-time inventory numbers as part of the CheckAvailabil-ityResponse</td></tr><tr><td>May 1, 2018</td><td></td><td>Addition of dynamic pricing for CheckAvailabilityResponse</td></tr><tr><td>April 1, 2018</td><td></td><td>Addition of the SupplierProductTypeCode field as part of the Activity-ListRequest response</td></tr><tr><td>January 20, 2018</td><td>zapiPackage_DetermineMinimumDatesToBook</td><td>Deprecated the &#x3C;staggerDates></td></tr><tr><td>January 20, 2018</td><td>zapiPackage_SetActivity-ComponentDate</td><td><p>Guest Standby logic has been added to many API calls, standardization of the standby details, and extra logic to allow adding a guest to standby:</p><p></p><p>API REQUEST: </p><ul><li>&#x3C;bookingId> (optional)</li><li>&#x3C;addtoStandBy> (optional)</li><li>new logic to allow adding to standby when setting the component travel date</li></ul><p>API RESPONSE:</p><ul><li>&#x3C;standBy></li><li>&#x3C;numberOnStandBy></li></ul></td></tr><tr><td>January 16, 2018</td><td>Booking - Search Results Node</td><td><p>Addition of </p><ul><li>guestId </li><li>guestHashKey</li></ul></td></tr><tr><td>December 13, 2017</td><td></td><td>Removal of the deltaOnly parameter on availability requests.</td></tr><tr><td>August 14, 2017</td><td>zapiPackage_DetermineMinimumDatesToBook</td><td><p>New fields were added to the return data on this API call, for the stand by, namely, the number of guests currently on standby, and if standby is available for a particular leg of journey.</p><ul><li>&#x3C;numberOnStandby/></li><li>&#x3C;isStandbyAvailable/></li></ul></td></tr><tr><td>March 20, 2017</td><td>zapiProcessSingleTransaction</td><td>For credit card payments, the addition of the XML item . If currencies are configured in your system, then the Cart Object will return, for each currency, a converted total including tax, for each currency. This currency ID, can then be passed along to the payment processing, to indicate the credit card amount is to be trans-acted with a specific (non-based currency) denomination, and the con-verted amount. Currencies can also be configured or a specific payment gateway.</td></tr><tr><td>August 26, 2016</td><td><ul><li>zapiGetPackagesByCategoryId</li><li>zapiGetPackageDetailsByPackageId</li><li>zapiGetActivitiesByCategoryId</li><li>zapiGetActivityDetailsByActivityId</li></ul></td><td>Addition of verboseMode flag to the following API calls, default value in all cases is true.</td></tr><tr><td>August 21, 2016</td><td>zapiGetActivityDetailsByActivityId, zapiAddActivityTo-Cart</td><td>Addition of supplierConfirmationNumberSystemManaged and sup-plierConfirmationNumberDisplayed fields indicating how remote supplier confirmation numbers are handled for each activity.</td></tr><tr><td>August 14, 2016</td><td>zapiBookings_CancelBooking</td><td>Addition of a new API call, allowing for cancellation of a booking within the system.</td></tr><tr><td>August 11, 2016</td><td><ul><li>zapiPromoCodeApply</li><li>zapiGiftCertificateApply</li></ul></td><td>Added as part of the returned payload on applying a promo code, the cart/order object.</td></tr><tr><td>August 3, 2016</td><td>zapiProcessSingleTransaction</td><td>Fixed misspelling of XML nodes.</td></tr><tr><td>August 1, 2016</td><td>zapiGetSystemInformation</td><td>Addition of airlines that are configured within the system.</td></tr><tr><td>July 29, 2016</td><td>zapiGetSystemInformation</td><td>Addition of the passengers configured as part of the overall system settings.</td></tr><tr><td>July 21, 2016</td><td></td><td>Remove Supplier Confirmation Number add as part of API calls where the system returns details of any single activity component, part of a booking, or an existing cart order. The field is called supplierConfirmationNumber, which describes the booking reservation number returned from a remote Zaui system, and is part of the Zaui to Zaui project.</td></tr><tr><td>July 21, 2016</td><td>zapiGetActivityDetailsByActivityId</td><td>Addition of new fields operatedByCompanyId and operatedByCompany-Name which describe the operating company for any given activity.</td></tr><tr><td>July 18, 2016</td><td>Activities Node</td><td><p>Addition of:</p><ul><li>isFreeSell</li><li>ticketExpiry</li><li>ticketPrinterText</li></ul></td></tr><tr><td>June 8, 2016</td><td>zapiGetActivitiesByCategoryId</td><td><p>Addition of: </p><ul><li>categoryName,</li><li>imageUrl </li><li>description</li></ul></td></tr><tr><td>June 2, 2016</td><td><ul><li>zapiProcessCartWithPayment</li><li>zapiProcessSingleTransaction</li></ul></td><td>Addition of the agent Id, that can be passed through for payment transactions that provision for the company ID and agent ID, such as vouchers (optional)</td></tr><tr><td>May 9, 2016</td><td></td><td>Addition of rental activity details as part of the returned search details</td></tr><tr><td>May 6, 2016</td><td></td><td><ul><li>Updated the documentation and return data for any search result, specifically the data returned within a single booking, when calling any of the search routines on the API</li><li>Added in the section defining the standardized booking data returned as part of the search results.</li><li>Addition of transaction details as part of the returned data set for to search results (via booking number, last name, mobile phone) </li><li>On all search results, added the agent details responsible for the booking, their name and company.</li></ul></td></tr><tr><td>March 14, 2016</td><td>zapiAddProductToCart</td><td>For percentage based product, you can now indicate a linked activity or package, also added to that, for which to base the product price.</td></tr><tr><td>March 4, 2016</td><td>zapiPackage_DetermineMinimumDates-ToBook</td><td>New Call: This routine helps determine, based on a package, and seed date, if all components of the package are bookable.</td></tr><tr><td>February 23, 2016</td><td>zapiGetPackageDetailsByPackageId</td><td><ul><li>New field: packageType – see package types appendix</li><li>New Appendix for package type descriptions </li><li>New Appendix for product type descriptions </li><li>New XML node that describes a single price code </li><li>New XML node that describes the configuration for multi-day itinerary based packages</li></ul></td></tr><tr><td>February 23, 2016</td><td>zapiPackage_RetrievePricingRates</td><td>Addition of a new API call which will return a complete XML description of all pricing components and details for a single package, regardless of sale or travel date.</td></tr><tr><td>February 22, 2016</td><td>zapiGuests_GetBookingDetails</td><td>Addition of onStandby, onWaitList, waitListId fields</td></tr><tr><td>February 22, 2016</td><td>zapiGetPackageDetailsByPackageId</td><td>Addition of optional seed package date when called</td></tr><tr><td>February 1, 2016</td><td>zapiGuests_UpdateProfile</td><td>Addition of updating a guests gender on the API</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zaui.com/zapi/getting-started/api-specification-enhancements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.