MIDAS API

API Release Notes

v2.18
15th April 2017Change: "get_venues" call now sorts venues in the order they're currently arranged in within MIDAS (rather than in the order they were added to MIDAS)
Updated: MIDAS v4.15 compatibility
Improved: API now returns 401 Unauthorized http status code when invalid API key specified
Improved: API logging now also includes more readable timestamps
Improved: API logging now indicates http request method
Improved: API logging now indicates size of JSON data response
Fixed: Tabs not correctly escaped in JSON responses
Fixed: Timestamps may not correctly reflect timezone setting
Fixed: "del_booking" and "del_bookings" API calls made without the "force" parameter set may allow bookings to be deleted multiple times
Fixed: "del_booking" and "del_bookings" API calls made without the "force" parameter may not correctly update the booking's history record
v2.17
9th March 2017Fixed: "get_availability" call may return "unknown venue" error
v2.16
8th March 2017Fixed: "del_booking" and "del_bookings" calls may not correct log to Recent Activity
v2.15
2nd November 2016Updated for MIDAS v4.14 compatibility
Fixed: "get_availability" wouldn't check dates in the past
v2.14
25th July 2016Added: "get_venues" call to retrieve all venue IDs/names
Improved: "get_bookings" call can now also accept a venue ID (or comma separated list of venue ID's) instead of a venue names for the "venue" parameter
Improved: "get_bookings" call now also returns internal venue ID in "venue_id" parameter
Improved: "get_venue" call now also returns internal venue ID in "id" parameter
Improved: "get_venue" call now also accept a venue ID instead of a venue names for the "venue" parameter
Improved: Handling of database connection errors
v2.13
12th July 2016Added: Support for client credit & invoice discounts
Improved: Validation of API Key
v2.12
24th February 2016Improved: Character set for responses now implicitly set to UTF-8
v2.11
10th February 2016Added: "authenticate_user" call
Added: Support for actioning API calls under individual user accounts
v2.10
28th January 2016Updated for MIDAS v4.11 compatibility
Added: Support for passing API key via an X-API-KEY HTTP header
Improved: "get_user" call now returns "max_booking_length" and "max_bookings_per_date" permissions
Improved: The API will now automatically reject non-GET/POST http methods
v2.09
18th August 2015Updated for MIDAS v4.10 compatibility
v2.08
13th July 2015Improved: "get_bookings" call can now be restricted to an individual client
Change: "get_client" call now returns "id" in place of "client_id"
v2.07
22nd May 2015Added: "get_resource" call
Improved: "get_venue" call now returns blocks and alternatives
Improved: Logging when calls fail/error produced
v2.06
28th February 2015Fixed: Some JSON responses don't correctly validate
v2.05
10th February 2015Fixed: Some settings not being correctly loaded if API run in isolation (without a concurrent login)
v2.04
9th February 2015Fixed: New line characters not being correctly escaped in some API responses
v2.03
1st February 2015Fixed: Quotation marks not being correctly escaped in some API responses
v2.02
19th January 2015Fixed: If multiple databases are in use, it may not be possible to access the Manage Addons screen from additional databases
v2.01
2nd January 2015Fixed: Multi-database support
v2.00
1st September 2014The API now allows bi-directional communication with MIDAS - meaning you can now add/set/change data as well as reading it.
The following new API calls have been implemented:
v1.03
20th March 2014Added: "member_of" to the list of returned values for the "get_venue" call
Change: Format of "rates" information returned by "get_venue" call updated for MIDAS v4.06
Fixed: "closed_from"/"closed_to" values from "get_venue" call may return 1/1/1970
v1.02
18th February 2014Added: Support for multiple databases
v1.01
7th October 2013Added: "get_venues_in_use" call
v1.00
1st June 2013Initial release of the MIDAS API Access Addon (for MIDAS v4.03+)