Table of Contents
- API Usage Guide
- API Command Reference
- add_booking
- add_client
- add_invoice
- add_resource
- approve_request
- authenticate_user
- del_booking
- del_bookings
- del_client
- del_invoice
- del_resource
- email_client
- gen_invoice
- get_activity
- get_availability
- get_booking
- get_booking_type
- get_booking_types
- get_bookings
- get_client
- get_consumable_levels
- get_invoice
- get_invoices
- get_messages
- get_reminders
- get_resource
- get_resource_availability
- get_setting
- get_template
- get_user
- get_users_logged_in
- get_venue
- get_venue_groups
- get_venues
- get_venues_in_group
- get_venues_in_use
- get_watches
- mod_booking
- mod_client
- mod_invoice
- mod_resource
- mod_venue
- notify_user
- reject_request
- restore_booking
- set_setting
- set_template
- util_api_usage
- util_from_epoch
- util_to_epoch
- Appendix A - Activity Codes
- Appendix B - Setting Names
- Appendix C - Error Handling
- Code Samples
- Troubleshooting
- Release Notes
← Hide Table of Contents
MIDAS API: del_booking
MIDAS API: del_bookingAvailable in API 2.0+
Deletes a single booking.| Required Parameters | Possible Values | Description |
| id | Number | The unique numerical reference of the booking to be deleted (which can be determined from the "get_bookings" call) |
| Optional Parameters | Possible Values | Description |
| force | 0 | 1 | By default, when a booking is "deleted", it still persists in a "hidden" state (allowing it to be restored at a later stage). Passing the "force" parameter with a value of "1" will mean that the booking will be completely removed from the system |
| no_watches | 0 | 1 | Setting the "no_watches" parameter to "1" will suppress generation of Watch notifications for users who are monitoring deleted bookings, otherwise omitting this parameter (or setting it to "0") will allow Watch notifications to be generated accordingly |
| Example Response |
{
"bookings_deleted":"1"
} |
| Variables Returned | Description |
| bookings_deleted | The number of bookings deleted |