Connect eQSL

Use your own eQSL account to send logged contacts and bring confirmation status back into Hamtrax. Every operator connects their own account; Hamtrax does not put everyone's contacts into a shared eQSL account.

Connect your account

1. Open Settings → Integrations → eQSL.
2. Enter your eQSL callsign and password, then connect. These are your eQSL credentials, rather than an API key.
3. If Hamtrax asks for a QTH profile, enter its grid square. Use the exact QTH nickname saved in eQSL when you have multiple profiles. Leave the nickname blank only if you have a single profile with no nickname. Use the location at which you operated, rather than assigning a home profile to a portable contact.

You can connect separate QTH profiles and choose between them on the eQSL page. Hamtrax validates the login before storing the password encrypted on its server. The saved connection works from your signed-in Hamtrax devices. Connecting alone does not send your existing logbook or import history.

Open connection management to update a saved login or disconnect a profile. Disconnecting stops new authenticated work and removes that profile's saved credentials; contacts and duplicate-protection records remain. A request already sent may still finish.

Send contacts

After Hamtrax confirms your eQSL connection, expand a saved contact's actions and choose Send to eQSL. The same review is available for a selected group of contacts or a whole folder. Send actions stay hidden while disconnected or while the connection cannot be confirmed.

Choose an appropriate connected profile, or let Hamtrax identify one from the saved station and location. Review how many contacts are ready to send, already sent, or need attention before confirming. Missing location evidence may require an explicit one-time profile choice; a profile that conflicts with known location information stays blocked. Neither choice rewrites the contact's saved location. Pending local changes must reach Hamtrax's server before they can be submitted.

Confirmation queues the upload. Open the eQSL workspace to see its progress and any issues. Sent means eQSL accepted the contact or already had it; it does not mean the other operator has confirmed your contact. A contact eQSL refuses is marked failed without holding up the rest. If eQSL's reply is lost, Hamtrax checks your eQSL Outbox a few times over the next several hours rather than uploading it again; if the contact still isn't there, it's marked failed and you can send it again. Editing a previously sent contact does not automatically replace its record on eQSL.

Receive confirmations

On the eQSL page, request a confirmation sync for the selected profile. Hamtrax marks an existing contact only when callsign, station callsign, UTC date and time, band, and mode identify one matching contact, with satellite and propagation details checked where present. A report that supplies seconds must match those seconds; a minute-only report uses that minute. An incoming card by itself does not create a new contact in your logbook. Unmatched confirmations, and any that can't be saved, remain private and are tried again during later syncs; the rest of the sync still finishes.

Confirmed contacts show eQSL received. Expand your contact and select eQSL details to see the recorded profile, delivery or receipt details, and the other operator's message when available. An imported ADIF confirmation flag can exist without private delivery receipts in Hamtrax.

The eQSL Authenticity Guaranteed designation identifies the sender's eQSL identity status. It is separate from LoTW confirmation. Private eQSL receipts and messages are not shown on your public Showcase.

Import your history

Use the history-import section of the eQSL workspace to preview your authenticated Outbox history. If Hamtrax asks for a file, download your Outbox as ADIF on eQSL and choose that file here instead. Review how many contacts are ready, already exist, or need attention, then confirm the import.

Use your sent-contact Outbox, rather than an Inbox file of cards received from other operators. Existing contacts are skipped, and incoming contacts still have to pass Hamtrax's normal filing and duplicate rules. Contacts that cannot be safely filed stay out of the logbook.

Confirming the import remembers the selected Outbox profile for new contacts that lack location evidence, allowing later confirmations to match. It does not fill in a missing operating grid, and known station or location contradictions still hold the contact for attention.

One history report can contain up to 20,000 contacts and 8 MiB of ADIF. An oversized report stops with an error rather than importing only part of it. The preview counts cover the complete accepted report; long destination and attention lists show a bounded summary with the full totals.

Optional automatic work

Each QTH profile has separate controls for automatic sends and confirmation checks. Both start Off, including after you replace a login. Automatic sending covers eligible contacts created after you turn it on; use a manual upload review for older contacts. Turn on only the behavior you want; history import remains an explicit preview and confirmation. Automatic work runs on Hamtrax's server, so leaving the page does not stop it. Turning a control Off stops further automatic work once the server receives the change; an upload already sent can still finish.

Card artwork and Share

Received eQSL card artwork is not available inside Hamtrax yet. The existing Share action generates a Hamtrax contact card with your contact details and map; it is separate from the card another operator sends through eQSL. Sending a contact to eQSL does not send that Hamtrax-generated image.