Building API Docs

[Jonneal3]

Hi all - I dont know about you, but I've got many clients interested in API docs to go along with ChatbotUI. For example, to utilize an assistant in ChatbotUI from a CRM for example, it is ideal to access the Chatbot UI Assistant from a webhook (at least for my clients). They can send out the actual message in their CRM, but the AI response behind it, would be cool to use a chatbot UI assistant.

I've already got a version of something that performs an assistant completion (tool and/or file), much like it does within chatbot UI, but via API.

I am going to make it open source. I was going to bake it into the Chatbot UI git here, but I think separating them might be a better idea for a few reasons - Mainly in that it is possible you will want to branch off hosting providers for your front end and API's. API's can be subject to DDOS attacks etc and it is probably advised in the long run to setup a kube cluster/LB to handle those request if you plan on using those in volume( i can help with this and maybe ill make a video).. Also, being that the there is not much front end work in the API routes, most of the UI framework is not necessary. Pllus, im not the MOST familiar with front end UI's yet as well and I dont want to screw anyhting up with what Mcckay already has in building endpoints lol :)

Anyways, I've got most of the actual code built out (have to adjust for a standard Chatbot UI DB schema), but Im not sure how I should best tackles the API docs. Theres swagger etc., but it would be nice to give users a "prettier" version of api docs to use... Any suggestions for the docs? Will post back at some point soon with some updates. Thoughts on all this? Jon