SOTAData Api Info?

I’m trying to find API documentation but I the Docs page that is referenced in several threads seems no longer to exist, although the API itself seems to be working. Is there an updated API reference around somewhere?

Thanks!

-Tony

https://api2.sota.org.uk/docs/index.html

1 Like

There aren’t any docs. You have to inspect them for yourself (or get the list from someone’s previous inspection).

Or check how others did that – go to any website using the API, e.g. sotl.as, enable the debugging console in Safari, and figure out a lot from there.

Tony @KM6AM

For what it’s worth I created a NodeRed app that runs on a Rpi that scrapped spots and tuned my KX2. Node-Red Calling Summit to Summit - Wanderings NodeRed made it very easy to “see” the JSON spot info and generally the fields names were easy to understand. Hence docs weren’t really that necessary.

However, now that we’ve moved beyond the software development stone age, I used Google CoLab to create a handful of demonstration apps in Python that parsed POTA and SOTA spots etc etc.

GenAI is your friend and it was quite mind boggling what the backend LLM figured out. I reviewed the Python, but Google Gemini did some very series magic. Hope that helps!

1 Like

I’ll add that Im hoping to be able to pull recent chaser logs. I’m currently ingesting spots from sota and rbn to create real time propagation maps and to see what I can hear from home. I was hoping to add a layer based on searching for new chases of the active summits, which I know could be easily accomplished with an SQL query, I’m wondering if there is an efficient way to do it. The app I made (vibe coding experiment) is in prototype form at km6am.com

This assumes chaserlogs are updated in real time. Many chaserlogs are batch submitted once a day/week/month etc.

1 Like

Agree that there are limitations, but I know I usually chase from sotawatch and log via the website and expect at least some others do to. I figure some information is better than none!

Wouldn’t it be simpler to extract who has been spotted from SOTAwatch and feed those calls into RBN’s map program to show where that station was heard. That way you beat RBN’s database and API to death and not ours?

2 Likes

I already pull spots from sotawatch and rbn via the telnet clusters, but I guess I don’t use the spotter call, that’s a good idea. I only hit the SOTA database for summits, and those are cached (currently with infinite ttl) so I don’t hit it too hard.

Are there any guidelines on appropriate/inappropriate API usage? I looked but couldn’t find anything.

If you use the Contact Form you can request access etc.

3 Likes