Delete Request - Plugixa Testimonial for WordPress

Delete Request - Plugixa Testimonial

DELETE /plugixatestimonial/v1/requests/{id}

Delete a request for good. Its link stops working; a testimonial already submitted through it is kept.

Administrators only: the user needs WordPress’s manage_options capability. No plugin capability opens this route.

Note. There is no existence check: an id that matches nothing still answers 200 with the success message, and nothing changes.

Request

DELETE https://your-site.example/wp-json/plugixatestimonial/v1/requests/15

Path parameters

Name	Type	Description
`id`	`integer`	The request’s id

Responses

`200` OK.

{
  "success": true,
  "message": "Request deleted.",
  "data": null
}

Field	Type	Meaning
`message`	`string`	A human-readable confirmation, translated to the site language

Errors

Status	Code	When
`500`	`rest_error`	The database refused the delete.

Plus the errors every endpoint can return.

Examples

curl -s -X DELETE "https://your-site.example/wp-json/plugixatestimonial/v1/requests/15" \
  -u "admin:$WP_APP_PASSWORD"

<?php
$ch = curl_init('https://your-site.example/wp-json/plugixatestimonial/v1/requests/15');
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/plugixatestimonial/v1/requests/15', {
  method: 'DELETE',
  headers: {
    'Authorization': 'Basic ' + btoa(`admin:${process.env.WP_APP_PASSWORD}`),
  },
});
const { data } = await response.json();