![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
0·
4 days agoLooks like the best openapi front. I looked into using it, but it didn’t seem free. Too bad this one is outdated. Lemmys API has changed quiet a bit since then.
Looks like the best openapi front. I looked into using it, but it didn’t seem free. Too bad this one is outdated. Lemmys API has changed quiet a bit since then.
(Author btw)
Can you expand on this? This was written for Kotlin usage. It automates generating API based on this spec.
I have no idea what you mean with ‘using other approaches to calling the endpoints’
Lemmy has only one API. It’s same API used for lemmy-ui.
This is just a “better” documentation for it.
The API works for for cloudfare instances too.
There is also a swagger ui variant
I do not see how critisms for the JS API docs are relevant for my openapi documentation.
This documentation aims to solve all those problems in a language agnostic way. It descibes the endpoints, the request object, the status, the response object, the authentication needed in visual/text. It allows you test it right from the browser, allows you to copy a working curl command, search for endpoints based on keywords, allows you to import the entire spec into postman/alts.
I ve never had any problems with CF instances but I mostly test with voyager.lemmy.ml