Read about the latest improvements and features we've added to the Premier API for partners and integrators.
We regularly review client feedback and support issues. The following items have been resolved in this release.
When a package timeband that was previously bookable is de-activated (by changing the times back to 00:00) this could cause the /Package/Search endpoint to hang with high CPU usage. This issue has been corrected.
Our ref: API-88
endpoint no longer returns an "Invalid Credentials" response if the credentials are correct and the latest user password has expired.
Our ref: API-40
We have fixed a divide-by-zero error when creating a bill that has no monetary value.
Our ref: API-100
An Internal Server Error has been resolved in the /Bill endpoint when a payment method was not provided.
Our ref: API-82
We have amaneded the API to look at the the promotion codes for reservations
Our ref: API-99
When posting or patching a reservation with a new package, the package ID is now validated that it is allocated to the site the reservation is due to take place at.
This prevents a 500 Internal Server Error and now returns a 400 Bad Request with the message "The package ID 'X' is not valid or is not allocated to site ID 'Y'".
Our ref: API-102
Invalid payment method IDs passed to the /Bill endpoint now return a validation message instead of a 500 Internal Server Error.
Our ref: API-108
A new property SelectionDetails has been added to the PackageItemDTO. On the /Package and /Reservation endpoints, if a package item is a selection, you will now get a new SelectionDetails property containing the ID of the selection itself.
We have also renamed the "PackageSiteReservationSelectionID" property in the /Finalise endpoint to simply "SelectionID". You should continue passing the selection's "ItemID" as returned from the /Reservation endpoints into this property.
Our ref: API-64
The Payment Method is no longer set to Web Payment against individual bill lines.
Our ref: API-72