Skip to main content

Get Your QRZ Logbook API Key

To import contacts from QRZ.com or upload Hamtrax contacts directly to it, Hamtrax needs your QRZ Logbook API key -- a per-logbook secret that grants read/write access to that one logbook. You connect it once; there is no separate vault passphrase or unlock step.

Requires a QRZ XML Logbook subscription

The Logbook API is a paid QRZ feature. You'll need an active QRZ XML Logbook subscription on the account that owns the logbook. Callsign lookups are already built into Hamtrax and do not require this.

1. Sign in to QRZ.com​

Log in to QRZ.com with the account that owns the logbook you want to connect.

2. Open your logbook settings​

  1. Go to your logbook at logbook.qrz.com.
  2. Use the logbook selector in the top-left to pick the logbook you want to connect -- each logbook has its own key.
  3. Click the Settings tab.

3. Reveal and copy the API key​

Scroll to the QRZ Logbook API section near the bottom of the Settings page. Your key is on the API Key row -- click Show to reveal it, then copy the full value.

Treat the key like a password

As QRZ notes on this screen, the key allows full read/write access to this logbook -- anyone who has it can add or delete your contacts. Hamtrax does not expose a QRZ delete action, but you should still keep the key private.

4. Connect it to Hamtrax​

  1. In Hamtrax, open Settings → Preferences → Integrations → QRZ Logbook.
  2. Paste the key into QRZ Logbook API Key.
  3. Click Connect QRZ.

Hamtrax verifies the key with QRZ before saving the connection. Once connected, you can import or upload from any device where you are signed in to the same Hamtrax account -- no repeated unlock step.

If you used the old QRZ vault

Paste the API key once more to create the new server connection. Hamtrax never stored the old vault passphrase, so it cannot migrate that encrypted key automatically. After the new key is validated and saved, Hamtrax removes the obsolete local QRZ vault from that device.

How the connection is protected

Your key travels to Hamtrax over an encrypted connection, is encrypted again before it is stored server-side, and is never returned to the app. When you request a QRZ status check, import, or upload, the authenticated Hamtrax gateway opens the key only long enough to make that QRZ request over HTTPS. Disconnecting QRZ removes the stored key.