Delete Space - Plugixa Car Parking

DELETE /plugixa-car-parking/v1/location-spaces/{id}

Move a space row to the trash. Its spaces stop counting towards availability.

The user needs the plugixa_carparking_delete capability.

A space row that upcoming bookings are held to cannot be trashed: move or cancel those bookings first, or set the row to inactive. An upcoming booking is one that has not ended yet, whose status holds a space (by default pending, confirmed, paid and completed), and whose payment hold has not expired. Only bookings held to this particular row count, which in practice means identified spaces PRO.

A trashed row can be brought back, or deleted for good: see the trash.

Note. Deleting for good skips the upcoming-bookings check: a space that bookings are still held to can be deleted for good.

Request

DELETE https://your-site.example/wp-json/plugixa-car-parking/v1/location-spaces/31

Path parameters

Responses

200 OK. The row is in the trash.

{
  "success": true,
  "data": {
    "trashed": true
  }
}

Errors

Plus the errors every endpoint can return.

Examples

curl -s -X DELETE "https://your-site.example/wp-json/plugixa-car-parking/v1/location-spaces/31" \
  -u "admin:$WP_APP_PASSWORD"

<?php
$ch = curl_init('https://your-site.example/wp-json/plugixa-car-parking/v1/location-spaces/31');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST  => 'DELETE',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_USERPWD        => 'admin:' . getenv('WP_APP_PASSWORD'),
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);

const response = await fetch('https://your-site.example/wp-json/plugixa-car-parking/v1/location-spaces/31', {
  method: 'DELETE',
  headers: {
    'Authorization': 'Basic ' + btoa(`admin:${process.env.WP_APP_PASSWORD}`),
  },
});
const { data } = await response.json();