Delete several booking requests at once. Provide ids, or explicitly set include to false with an event or parent filter to delete every request matching the filters; without one of those the request is rejected with 400, as is an empty body. With the Full Write Facilities permission you can delete any request; otherwise only callers who can administer the associated event can: events writers at its campuses within their calendar limit, and the event's admins (organizers, administrators of its group, group members with the Events flag). While multi-campus or multi-org limits apply, a selection by ids or by filtering on event deletes the requests of each event you administer at any location, whatever the selected campus lens, and the others keep the campus filter; a holder deletes at campuses where they hold it, and at a venue only while holding it across the venue's whole scope or running the request's event. Explicit ids that include a request at a venue the holder cannot delete answer 403 with no_campus_rows_record_delete_desc while multi-org is on and every_campus_record_delete_desc while it is off, and nothing is deleted; include false leaves such requests in place. The response reports how many were deleted and how many of the requests the caller can see were left in place.
Required permission: Full Write Facilities
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
401Authentication is required, or the Ocs-Api-Key header is missing or invalid.
