QSO

The QSO resource lets you read, create, update and delete log contacts. It builds on the same logbook engine as the web UI, so dupe handling, mode/submode splitting and teardown on delete all behave exactly as they do in Wavelog itself.

• Base path: /api/v2/qso
• Scopes: qso:read, qso:write, qso:delete

All operations are scoped to the token owner's station locations. A QSO that does not belong to one of them is treated as not found.

Endpoints

Frequencies

Frequencies (freq, freq_rx) are expressed in Hz throughout the JSON API — in create bodies (single and bulk), in update bodies and in responses. You may also pass a value with a unit suffix, e.g. "7.0475M", which is parsed to 7047500 Hz.

The QSO object

Responses return this shape (from the logbook record):

{
  "id": 4886,
  "station_id": 1,
  "call": "N9EAT",
  "band": "20m",
  "mode": "SSB",
  "submode": null,
  "freq": 14075000,
  "freq_rx": null,
  "qso_date": "2026-06-16 17:06:00",
  "rst_sent": "59",
  "rst_rcvd": "57",
  "gridsquare": "EN42",
  "name": "Marty",
  "comment": "",
  "notes": "",
  "qth": "",
  "prop_mode": "",
  "sat_name": ""
}

List QSOs

GET /api/v2/qso

The list endpoint takes a common set of filters and renders the result either as JSON (default) or as ADIF — the data is fetched once and only the format differs (see Export QSOs as ADIF).

Filters (all optional):

qso_since and qso_until filter on the QSO date, are inclusive on both ends and can be used on their own or as a pair. They are independent of since_id, which walks the database primary key for incremental syncing. A malformed date returns 400 validation_error.

Pagination and rendering:

per_page is the batch-size knob for both formats. Only the default differs — small for JSON browsing, larger for ADIF bulk sync — while the maximum is the same 5000.

Use limit when you just want the latest few contacts: it returns the newest N QSOs (newest first, after any filters), ignoring page/per_page. It is capped like per_page (5000).

# Your most recent QSO
curl "https://<WAVELOG_URL>/index.php/api/v2/qso?limit=1" \
     -H "Authorization: Bearer wl2_your_token_here"

curl "https://<WAVELOG_URL>/index.php/api/v2/qso?band=20m&station_id=1&per_page=100" \
     -H "Authorization: Bearer wl2_your_token_here"

# Everything logged in June 2026
curl "https://<WAVELOG_URL>/index.php/api/v2/qso?qso_since=2026-06-01&qso_until=2026-06-30" \
     -H "Authorization: Bearer wl2_your_token_here"

{
  "data": [ { "id": 4886, "call": "N9EAT" } ],
  "meta": { "page": 1, "per_page": 100, "count": 1, "total": 1, "total_pages": 1, "has_more": false }
}

The JSON list is ordered newest first. The meta block carries the full pagination state — total, total_pages and has_more — so you can page until has_more is false without probing for an empty page. See Pagination for the field reference.

Export QSOs as ADIF

GET /api/v2/qso?format=adif

Renders the same filtered result set as the list above, but as ADIF instead of JSON — so all the list filters (station_id, callsign, band, mode, qsl_filter, since_id, qso_since, qso_until) apply. This is the v2 equivalent of the v1 get_contacts_adif endpoint.

The batch size is per_page — for ADIF it defaults to 1000 (up to the shared 5000 maximum). For ADIF the rows are ordered ascending by id, and the response reports lastfetchedid (the highest id in this page). Feed it back as the next request's since_id for an incremental sync that only ever pulls new contacts — or page with page/per_page and the meta.has_more flag.

curl "https://<WAVELOG_URL>/index.php/api/v2/qso?format=adif&since_id=0&station_id=1&per_page=1000" \
     -H "Authorization: Bearer wl2_your_token_here"

{
  "data": {
    "exported": 3,
    "lastfetchedid": 3218,
    "adif": "Wavelog ADIF export\n<ADIF_VER:5>3.1.7\n…<EOH>\n…<EOR>\n"
  },
  "meta": { "page": 1, "per_page": 500, "count": 3, "total": 3, "total_pages": 1, "has_more": false }
}

When there is nothing new, exported is 0 and adif is null.

Fetch a single QSO

GET /api/v2/qso/{id}

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

Returns 404 not_found if the QSO does not exist or is not owned by the token — and, for a clubstation token below officer level, if it was logged by a different operator.

Create a QSO

POST /api/v2/qso

The optional body field import_type selects the payload format:

An unknown import_type returns 400 validation_error.

For a single json QSO, send the fields at the top level (not an ADIF string).

Required fields:

Common optional fields include freq, freq_rx, time_off, rst_sent, rst_rcvd, gridsquare, name, comment, and any other valid ADIF field name (lowercase). See Editable fields for the fields that PATCH recognises explicitly.

curl -X POST https://<WAVELOG_URL>/index.php/api/v2/qso \
     -H "Authorization: Bearer wl2_your_token_here" \
     -H "Content-Type: application/json" \
     -d '{
           "station_profile_id": 1,
           "call": "N9EAT",
           "band": "20m",
           "mode": "SSB",
           "freq": 14075000,
           "qso_date": "2026-06-16",
           "time_on": "1706",
           "rst_sent": "59",
           "rst_rcvd": "57",
           "gridsquare": "EN42",
           "name": "Marty"
         }'

On success the API responds with 201 Created, a Location header pointing at the new QSO, and the created object in data. Duplicate detection follows the normal logbook rules.

Import multiple QSOs (JSON)

POST /api/v2/qso with a qsos array (still import_type: "json").

To create several QSOs in one request, send a qsos array instead of top-level QSO fields. Each element is a QSO object with the same fields as a single create; they are all imported into the shared, top-level station_profile_id.

Body fields:

curl -X POST https://<WAVELOG_URL>/index.php/api/v2/qso \
     -H "Authorization: Bearer wl2_your_token_here" \
     -H "Content-Type: application/json" \
     -d '{
           "station_profile_id": 1,
           "qsos": [
             { "call": "N9EAT", "band": "20m", "mode": "FT8", "qso_date": "2026-06-16", "time_on": "1706" },
             { "call": "W1AW",  "band": "40m", "mode": "CW",  "qso_date": "2026-06-16", "time_on": "1712" }
           ]
         }'

The response is a bulk-import summary — the same shape as the ADIF import:

{ "data": { "parsed": 2, "imported": 2, "skipped": 0, "messages": [] } }

A missing required field in one row fails the request with 400 validation_error, and details.index points at the offending array element.

Import multiple QSOs (ADIF)

POST /api/v2/qso with import_type: "adif"

Bulk-imports an ADIF payload through the same engine the web UI and the v1 API use.

Body fields:

curl -X POST https://<WAVELOG_URL>/index.php/api/v2/qso \
     -H "Authorization: Bearer wl2_your_token_here" \
     -H "Content-Type: application/json" \
     -d '{
           "import_type": "adif",
           "station_profile_id": 1,
           "adif": "<CALL:5>N9EAT<QSO_DATE:8>20260102<TIME_ON:4>1300<BAND:3>20m<MODE:3>FT8<EOR>"
         }'

A real import returns 201 Created with a summary; a dryrun returns 200 OK with the parsed count:

{ "data": { "parsed": 1, "imported": 1, "skipped": 0, "messages": [] } }

{ "data": { "dryrun": true, "parsed": 1 } }

If nothing could be imported and only hard errors occurred, the API returns 400 validation_error with the details.

Update a QSO

PATCH /api/v2/qso/{id} — partial update, only the fields you send are changed. Anything you omit keeps its stored value.

curl -X PATCH https://<WAVELOG_URL>/index.php/api/v2/qso/4886 \
     -H "Authorization: Bearer wl2_your_token_here" \
     -H "Content-Type: application/json" \
     -d '{ "comment": "Nice ragchew", "rst_rcvd": "59" }'

The response returns the fresh state of the QSO in data.

Notes:

• qso_date and time_on must be supplied together. time_off defaults to time_on and is never earlier than it.
• Passing station_profile_id moves the QSO to another of your station locations (ownership is verified).
• With a clubstation token below officer level you may only edit QSOs you logged yourself; another operator's QSO returns 404 not_found.

Editable fields

PATCH accepts the following fields (in addition to qso_date/time_on, time_off, mode, freq/freq_rx and station_profile_id, which are handled specially):

call, band, band_rx, rst_sent, rst_rcvd, gridsquare, name, comment, notes, qth,
tx_pwr, prop_mode, sat_name, sat_mode, sota_ref, pota_ref, wwff_ref, iota, sig,
sig_info, darc_dok, state, cnty, cqz, ituz, qsl_via, srx, stx, srx_string, stx_string

Delete a QSO

DELETE /api/v2/qso/{id}

curl -X DELETE https://<WAVELOG_URL>/index.php/api/v2/qso/4886 \
     -H "Authorization: Bearer wl2_your_token_here"

Deletion runs the full teardown (OQRS entries, QSL/eQSL images, caches), exactly like deleting from the web UI. On success the API returns 204 No Content.

As with PATCH, a clubstation token below officer level may only delete its own QSOs; another operator's returns 404 not_found.