This might be something to deal privately but as I don’t have Manuel’s contact info, here it goes 
WWFF cluster services will change dramatically: the cluster at GMA will be shut down and new official spots & agenda web service is going to be launched 1st of June.
This means that HamAlert should change it’s interface where to get new spots. We are providing dxspider-clone “telnet” server and then json-source for the active spots too.
Also if interested, we could implement some custom push-service for HamAlert for superfast alerts (that would be really cool).
Anyway Manuel, I hope you contact so I can give you more info on this change
https://wwff.co/2025/05/announcing-spotline-wwffs-new-spot-agenda-service/
Hello Jouni,
Thanks for the heads-up!
What would be ideal for HamAlert is some sort of streaming endpoint (Telnet style, WebSocket etc.) that HamAlert can connect to in order to obtain spots asynchronously, ideally in JSON format.
The reverse (i.e. some external service pushing spots to HamAlert) does not work so well for HamAlert’s architecture. In both cases, the delay between spot submission at the source and processing by HamAlert will be the same, and very small. Much better anyway than polling, which HamAlert currently has to use for the SOTAwatch, POTA and WWFFwatch APIs 
73,
Manuel HB9DQM
Manuel,
we will have a DXspider-style server with traditional telnet-output, if that is fine for you?
Now thinking again, yes you are right, reverse/push style doesn’t really add anything if streaming is anycase used.
Currently our dev servers are down (because someone posted the URLs to Facebook), so perhaps you can look at this near launch date. I can provide a private test-server address you if you email me.
Yes, that will work. If it has an option to switch to JSON output instead of the traditional fixed-field-length DX cluster style, then all the better, but the latter will work as well.
Sounds good! You can reach me at mk@neon1.net.