Contents
On this page

List Report Schedules - Plugixa Activity Log

GET /plugixa-activity-log/v1/reports/schedules

List every scheduled report, sorted by name.

Needs settings access (see who can call what): administrators, and on multisite network administrators. Needs Plugixa Activity Log Pro, with the Reports module on under Plugixa Activity Log -> Monitors.

Request

GET https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules

This list is not paged and takes no parameters. On multisite, a caller who cannot see the whole network only gets the schedules created on their own site.

Responses

200 OK. data is every schedule.

{
  "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-09 07:00:04",
      "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-09 07:00:04"
    }
  ]
}
Field Type Meaning
data[].id integer The schedule’s id
data[].name string Its name, also the report title and the start of the email subject
data[].enabled boolean Whether it runs
data[].frequency string daily, weekly or monthly
data[].weekday integer Weekly runs: 0 (Sunday) to 6
data[].monthday integer Monthly runs: 1 to 28
data[].hour integer 0 to 23, on the site’s clock
data[].format string html or csv
data[].sections array The report sections, as for Run Report
data[].filters object|array The report filters. An empty [] when there are none
data[].recipients array Email addresses
data[].site_id integer The site it reports on, 0 for every site
data[].last_run_at string|null UTC datetime of the last send, null before the first
data[].last_status string sent, failed, or empty before the first run
data[].last_error string Why the last run failed, else empty
data[].next_run_at string|null UTC datetime of the next run, null when the schedule is off
data[].created_by integer The user who created it
data[].created_at string UTC datetime
data[].modified_at string UTC datetime of the last change or run

Each run covers the last complete period before it: yesterday for daily, the seven days before the run day for weekly, the previous calendar month for monthly. The report is emailed as an attachment.

Errors

Plus the errors every endpoint can return.

Examples

curl -s "https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules" \
  -u "admin:$WP_APP_PASSWORD"

<?php
$ch = curl_init('https://your-site.example/wp-json/plugixa-activity-log/v1/reports/schedules');
curl_setopt_array($ch, [
    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', {
  headers: {
    'Authorization': `Basic ${auth}`,
  },
});
const { data } = await response.json();

Quick Links

Share