Contents
On this page
Send Scheduled Report Now - Plugixa Activity Log
POST /plugixa-activity-log/v1/reports/schedules/{id}/run-now
Build a schedule’s report and email it to its recipients now, without waiting for its next run.
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 report covers the last complete period before now, exactly as a scheduled run would: yesterday for a daily schedule, the seven days before today for a weekly one, the previous calendar month for a monthly one. It does not include today.
Note. A manual send counts as a run. It updates
last_run_at,last_statusandlast_error, works outnext_run_atagain, and is recorded in the log as event 9004 (sent) or 9005 (failed). It also sends a schedule that is switched off.
Request
POST https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules/3/run-now
Path parameters
| Name | Type | Description |
|---|---|---|
id |
integer |
The schedule’s id |
No body.
Responses
200 OK. The email was handed to WordPress. data is the schedule after the run.
{
"success": true,
"data": {
"id": 3,
"name": "Weekly security summary",
"enabled": true,
"frequency": "weekly",
"weekday": 1,
"monthday": 1,
"hour": 7,
"format": "html",
"sections": ["summary", "by_severity", "events"],
"filters": { "min_severity": "high" },
"recipients": ["owner@example.com"],
"site_id": 0,
"last_run_at": "2026-11-12 09:30:00",
"last_status": "sent",
"last_error": "",
"next_run_at": "2026-11-16 07:00:00",
"created_by": 1,
"created_at": "2026-10-20 14:02:11",
"modified_at": "2026-11-12 09:30:00"
}
}
| Field | Type | Meaning |
|---|---|---|
data.last_run_at |
string |
UTC datetime of this send |
data.last_status |
string |
sent |
data.next_run_at |
string|null |
UTC datetime of the next scheduled run, null when the schedule is off |
“Sent” means WordPress accepted the email. Whether it reaches the inbox depends on the site’s mail setup.
Errors
| Status | Code | When |
|---|---|---|
404 |
plugixa_activity_log_not_found |
No schedule with that id, or, on multisite, one that belongs to another site. |
502 |
plugixa_activity_log_report_failed |
The report could not be built or WordPress could not send the email. The message is the reason, also stored in last_error. |
Plus the errors every endpoint can return.
Examples
curl -s -X POST "https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules/3/run-now" \
-u "admin:$WP_APP_PASSWORD"
<?php
$ch = curl_init('https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules/3/run-now');
curl_setopt_array($ch, [
CURLOPT_CUSTOMREQUEST => 'POST',
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/run-now', {
method: 'POST',
headers: {
'Authorization': `Basic ${auth}`,
},
});
const { data } = await response.json();
Quick Links
Share