is there an API to get the logged chaser QSOs for a Callsign?
What I did so far is downloading the logs from sotadata as CSV files and scraping them for summits that I chased, but not yet activated. In other words, I now have a list of summits, where just an activation would lead to the summit complete status.
It would be more concenient to get the required data from an API instead of manually downloading the logs.
and the other way around works perfect with hamalert.org:
you can set triggers for summits you activated (but have not chased so far) and get notified on your smartphone if a spot for one of these summits appears on SOTAwatch …
Where USERID is the numeric user ID for the callsign.
Your numeric user ID can be obtained from the SOTLAS web site (https://sotl.as). Sign into the SOTLAS web site, click your callsign in the upper right-hand corner of the page, and select “My activator page” from the drop-down menu. Click on the log for one of your activations (the icon under the QSOs column), and then hover your mouse over your callsign in the upper left-hand corner of the pop-up window. Your browser should display a URL for this link, which will be of the form https://sotl.as/activators/NNNN, where NNNN is your numeric User ID. If you don’t see this link, you may need to adjust a setting in your browser to display links on hover.
Thank you very much @ON6ZQ and @AK5SD! It works great. I already tested it out. Sad there is noting like “id_by_callsign”, but for me it works great now.
All of these are private APIs about to go through massive changes - please reach out to me via PM first so I can understand what you are trying to do and see if there’s a better way than just hitting random endpoints.
This is why people shouldn’t randomly send out private APIs because there is an endpoint for this, but it’s not used much any more because api-db is deprecated for all new usage and will vanish in coming months.