The API documentation should
slowly reveal it self here:

https://clrghouz.bbs.dege.au/docs/

Awesome!! Thanks!
Just ran some test requests and they worked!


--- NE BBS v1.11.1 (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Re: Re: HTTP API available on clrghouz
By: deon to paulie420 on Tue Aug 26 2025 12:33 pm

Howdy,

I have a description on it's home page:

https://clrghouz.bbs.dege.au/about

Did it make sense?


...ëîåï
--- SBBSecho 3.27-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

I have a description on it's home page:

https://clrghouz.bbs.dege.au/about

Did it make sense?

Perfect. :P Thanks for the share; I've also archived clrghouz.bbs.dege.au @ archivebox.20ForBeers.com.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Would you mind posting a summary of what clrghouz is - FTNs are my BBS weak point, but I'm interested in projects that support our community.

It's cool as hell!! One cool feature is, since my board doesn't support using QWK mail for anything besides offline readers, I can poll DOVENet like a normal Fido style net, and clrghouz handles the conversion.

I'm not even using a fraction of its power, either!!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hi Deon,
I was just curious if the API is going to be a permanent addition to clrghouz? I was thinking of reworking the code of my tosser to route netmails through it and only use binkd if for some reason the API call failed.

Thanks!


--- NE BBS v1.11.1 (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Re: Re: HTTP API available on clrghouz
By: slacker to deon on Sun Sep 14 2025 02:13 am

Howdy,

I was just curious if the API is going to be a permanent addition to clrghouz? I was thinking of reworking the code of my tosser to route netmails through it and only use binkd if for some reason the API call failed.

It is - I'll also add an API to post echomail, as well as one to download/upload a mail packet (so you dont need a mailer).

(I'm distracted on fixing my binkd implementation at the moment, so when that's done, I'll work more on API stuff).

Have you been using the netmail API? I've only implemented basic functionality, so want to be sure its robust before spending more time on other things (like responding to PING/AREAFIX, etc).

I'm also playing with rabbitmq (for no other reason other than I'm curios), and I'm goign to implement a rabbitmq<->rabbitmq link for other clrghouz hub to hub instances (well see if it is something that could work).

Was wondering if that might be good for a BBS, I think I saw javascript MQ clients so not sure how easy that might be to integrate with SBBS for example. For other mailers, a simple PHP script could pull mail out of the queue.

If only there were 48hrs in day... :)




...ëîåï
--- SBBSecho 3.27-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Thanks for confirming it's here to stay! I've used it successfully for testing but only testing.

I'll add it to my 'to-do' list to route my netmail through it. I don't actually send much netmail but it will be cool to have!

Having an upload/download endpoint for packets sounds good. On my side at least, it would save having the binkd dependency and polling with that, etc.


--- NE BBS v1.11.1 (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)