Developer resources

BBSlink clients exist for common platforms, but SysOps are encouraged to build native integrations for their own BBS software — and share them back with the community.

Connection flow

The BBSlink handshake happens in two stages:

  1. Authenticate over HTTP (your client identifies the system and user context)
  2. Connect via telnet (into the door server once authorised)

The PDF below contains process maps and worked examples.


Need a new “client type”?

If you’re planning a new client/script and need a client type enabled for authentication, get in touch and include your target platform + BBS software. We’ll make sure the server recognises it.

Good citizenship

  • Cache responses sensibly (don’t hammer endpoints)
  • Fail gracefully if HTTP is blocked by a host
  • Keep credentials out of logs
  • Make it feel native on the caller’s side

Share your client

If you publish your script on GitHub/Gist, send the link — we’ll add it to the SysOp resources page.