Upload QSOs and query logbook confirmations from a self-hosted Wavelog instance via its REST API
domain: wavelog.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In your Wavelog instance, generate a read-only or read/write API key from the account API settings page.
POST ADIF QSO data as JSON to https://YOUR_WAVELOG_HOST/index.php/api/qso with a body containing your API key, station_profile_id, type: adif, and the ADIF record string; note this does not trigger a live QRZ push or callbook lookup even if those are otherwise enabled for the account.
Use https://YOUR_WAVELOG_HOST/api/get_contacts_adif with a fetchfromid delta cursor to incrementally stream new QSOs as ADIF-in-JSON, rather than re-pulling the whole log each time.
Use https://YOUR_WAVELOG_HOST/api/private_lookup to check whether a specific callsign/band/mode combination has already been worked and/or confirmed (LoTW, eQSL, QSL, Clublog) in the account's own logbook.
Set Content-Type: application/json and Accept: application/json headers on every POST, and respect any instance-owner-configured rate limit rather than polling endpoints like /api/radio on every second.
Known gotchas
Wavelog is self-hosted, like Cloudlog, so the base URL is whatever domain the operator deployed to; there is no fixed public API host.
private_lookup only checks the API key owner's own logbook, not a global public 'has anyone worked this call' database; it is a personal duplicate/award-progress check, not a general lookup service.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?