Statistic

The Statistic resource is a read-only endpoint that returns flat, numeric counters. It is designed for dashboards and monitoring/alerting systems (for example Zabbix): each value has a stable JSONPath, so you can map it directly onto a monitoring item or trigger.

• Base path: /api/v2/statistic
• Scope: statistic:read

Endpoint

Query parameter:

Each topic is nested under its own key, so a value's JSONPath is identical whether you request the topic on its own or as part of full (e.g. $.data.qso.total). The response meta reports the requested profile and whether the token owner is an admin.

Topics

qso (default)

QSO analytics scoped to the token owner's station locations — these are your own numbers, not the whole instance.

curl "https://<WAVELOG_URL>/index.php/api/v2/statistic?profile=qso" \
     -H "Authorization: Bearer wl2_your_token_here"

{
  "data": {
    "qso": {
      "total": 28,
      "activity": { "today": 2, "month": 5, "year": 7 },
      "breakdown": {
        "by_band": [ { "band": "20m", "count": 12 } ],
        "by_mode": [ { "mode": "CW", "count": 7 } ]
      },
      "dxcc": { "worked": 15, "confirmed": 9, "available": 340 }
    }
  },
  "meta": { "profile": "qso", "admin": false }
}

by_band and by_mode return the top entries by count.

confirmations

QSL confirmation counts per confirmation type, broken down by band and by mode alongside the grand totals. Like qso, it is scoped to the token owner's station locations.

Unlike the other topics, confirmations accepts filters. They are all optional and can be combined:

since and qso_since answer different questions. since filters on the date a confirmation arrived — "how many confirmations came in this week" — and is applied per type against that type's own received-date column. qso_since/qso_until filter on the date of the QSO itself — "how many of my QSOs since January are confirmed", or paired, "how did last year's contest QSOs end up being confirmed". Both ends are inclusive and can be used on their own. They are the same filters as on the QSO list.

An invalid type value or a malformed date returns 400 validation_error. Note that HRDLog is not a confirmation type: Wavelog only uploads to it, there is no received status to count.

Every row carries two framing numbers next to the per-type counts:

Groups without a single confirmation are still listed — a band with QSOs and no confirmations is usually the interesting one. The filters object echoes back the resolved filters, so a poller can interpret the numbers without tracking the query it sent.

curl "https://<WAVELOG_URL>/index.php/api/v2/statistic?profile=confirmations&type=lotw,eqsl&since=2026-07-01" \
     -H "Authorization: Bearer wl2_your_token_here"

{
  "data": {
    "confirmations": {
      "counts": { "qsos": 2480, "lotw": 812, "eqsl": 430, "confirmed": 1024 },
      "by_band": [
        { "band": "20m", "qsos": 1120, "lotw": 402, "eqsl": 210, "confirmed": 501 },
        { "band": "40m", "qsos": 780, "lotw": 236, "eqsl": 118, "confirmed": 297 }
      ],
      "by_mode": [
        { "mode": "FT8", "qsos": 1503, "lotw": 610, "eqsl": 300, "confirmed": 700 },
        { "mode": "CW", "qsos": 640, "lotw": 202, "eqsl": 130, "confirmed": 324 }
      ],
      "filters": {
        "type": ["lotw", "eqsl"],
        "since": "2026-07-01",
        "qso_since": null,
        "qso_until": null,
        "band": null,
        "mode": null
      }
    }
  },
  "meta": { "profile": "confirmations", "admin": false }
}

Only the requested types appear in counts and in the breakdown rows. Summing a breakdown column always reproduces the matching value in counts.

Satellite QSOs are included and appear in by_band under their band; use band=SAT to look at them on their own.

system (admin only)

Version, build and instance internals — users, database and PHP versions, worker status, cache and process statistics.

{
  "data": {
    "system": {
      "wavelog": "2.0",
      "adif": "3.1.4",
      "migration_db": 287,
      "migration_config": 287,
      "database": "8.0.36",
      "php": "8.3.0",
      "environment": "production",
      "time": "2026-06-16 17:06:00",
      "wavelog_stats": { "users": 3, "stations": 5, "logbooks": 4, "radios": 2 },
      "system_stats": { "memory_usage": 8388608, "memory_peak": 10485760, "cpu_time": 0 },
      "cache": {},
      "worker": {
        "enabled": true,
        "client_url": null,
        "nodes": [],
        "nodes_alive": 0,
        "nodes_total": 0,
        "active_topics": 0,
        "connected_clients": 0
      }
    }
  },
  "meta": { "profile": "system", "admin": true }
}

full

Returns every topic the token is permitted to see. For a regular token that is qso and confirmations; for an administrator token it also includes system. The confirmations filters apply here too.

curl "https://<WAVELOG_URL>/index.php/api/v2/statistic?profile=full" \
     -H "Authorization: Bearer wl2_your_token_here"

Monitoring tips

• Poll a single cheap topic (profile=qso) rather than full when you only need a few values.
• Because JSONPaths are stable, you can point a Zabbix (or similar) item straight at, for example, $.data.qso.total or $.data.qso.activity.today. The same holds for the confirmation counters, e.g. $.data.confirmations.counts.lotw.
• To alert on incoming confirmations, poll profile=confirmations&since=<yesterday> and trigger on $.data.confirmations.counts.confirmed.
• Respect any rate limits the instance owner has set.