That's already possible rn for free because of the RSS feed
I started working on a API client by extracting all the SN specific code of @hn into a separate go module.
But a real API client should have all the features the frontend has like pricing, login etc. so I didn't post about it here.
Also, I am not sure if we already want to officially support such use cases so it makes sense to wait until we implement something more official which is more accessible by bots including API docs.
I understand the urge to deliver a complete API. Scoping APIs can be a challenge but I would encourage an MVP with just enough features to get feedback. It's a great benefit to already have sats balances to tap for API usage and who knows what value stream you might uncover.
reply
I get your point. I was just hesitant since people may assume this is something official and they can expect more work on this soon which is not the case. I mentioned the go module here now: #190140
reply