Contents
Delete Report Schedule - Plugixa Activity Log
DELETE /plugixa-activity-log/v1/reports/schedules/{id}
Delete a scheduled report. It stops being sent; reports already emailed are not affected, and no event is removed from the log.
Needs settings access (see who can call what). Needs Plugixa Activity Log Pro, with the Reports module on under Plugixa Activity Log -> Monitors.
Note. The deletion is permanent: there is no trash for schedules.
Request
DELETE https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules/3
Path parameters
| Name | Type | Description |
|---|---|---|
id |
integer |
The schedule’s id |
Responses
200 OK. The schedule is gone.
{
"success": true,
"data": { "deleted": true }
}
| Field | Type | Meaning |
|---|---|---|
data.deleted |
boolean |
Always true |
Errors
| Status | Code | When |
|---|---|---|
404 |
plugixa_activity_log_not_found |
No schedule with that id, or, on multisite, one that belongs to another site. |
Plus the errors every endpoint can return.
Examples
curl -s -X DELETE "https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules/3" \
-u "admin:$WP_APP_PASSWORD"
<?php
$ch = curl_init('https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules/3');
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 auth = Buffer.from(`admin:${process.env.WP_APP_PASSWORD}`).toString('base64');
const response = await fetch('https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules/3', {
method: 'DELETE',
headers: {
'Authorization': `Basic ${auth}`,
},
});
const { data } = await response.json();
Quick Links
Share