Upload QSOs and read logbook statistics from a self-hosted Cloudlog instance via its REST API
domain: magicbug.co.uk · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In your Cloudlog instance, generate a read-only or read/write API key from the user account menu, matching the permission level your integration needs.
POST ADIF-formatted QSO data as JSON to https://YOUR_CLOUDLOG_HOST/index.php/api/qso with a body containing your API key, station_profile_id, type: adif, and the ADIF record string.
Send a GET request to https://YOUR_CLOUDLOG_HOST/index.php/api/statistics/YOUR_API_KEY for read-only dashboard-style stats (today/month/year/total QSO counts) without needing an authenticated browser session.
Look up the correct station_profile_id beforehand from the station-profile edit URL in the Cloudlog web UI, since it is required on QSO-upload requests.
Consult the project's GitHub wiki (github.com/magicbug/Cloudlog/wiki/API) for the authoritative, current endpoint list, since Cloudlog is actively developed and endpoints can change between releases.
Known gotchas
Cloudlog is self-hosted; there is no single central API host, so the base URL is whatever domain the operator deployed their own instance to.
Because instance versions vary, some documented endpoints may not exist on an older deployment; check the running instance's version before assuming a given endpoint is available.
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?