Hi,
I maintain Nexus, a ham radio logging and operating program. It has a bit over a thousand active operators on Windows, Linux and Raspberry Pi, and it already uploads to LoTW, eQSL, QRZ, ClubLog and HRDLog.
Several of my users log to WRL and want their contacts to get there the same way. I read the API threads on your community. N0APX said it was on the roadmap in February 2025, and K4AZE said you were working on it this May. So I am asking rather than guessing at something undocumented.
If you are building it, I would like to test against it early. I can tell you what breaks before it goes public, and ship support the day it opens instead of months later.
Three things would make this straightforward on my end, based on the five connectors I already maintain.
First, ADIF over an authenticated HTTP endpoint. I already generate ADIF for every other service, so that part costs me nothing.
Second, an API key or token for each user rather than the account password. I keep credentials in the OS keychain and would rather not hold anyone’s WRL login.
Third, a response that tells accepted, duplicate and auth failure apart. That is what lets a retry know whether it actually worked.
Your duplicate detection already covers the case I would otherwise worry about most, so that side looks well thought out.
In the meantime, Nexus already sends the WSJT-X UDP protocol your CAT Control app listens for, so that route should work today. I will document it for my users either way.
Happy to talk wherever suits you, and glad to test under embargo if the API is not public yet.
73,
KD9TAW