disclaimer: this is a bit of a rant and i may not be aware of the correct resources to look at. if i am missing something obvious please feel free to call me an idiot and link me the good docs :smiley: i gotta be honest: as much as i love fibery so far, not having the api documentation in this form…

A couple of things worth saying: Fibery terminology has changed over the years, so what are now called Spaces used to be called Apps, Databases used to be called Types. Changing the API to reflect that has not been a priority the inherent flexibility of Fibery means that API syntax will vary heavi…

I’m glad to see someone else chiming in on the topic. I’ve been working with the Fibery API regularly since 2021. My skill level at that time was beginner, today I’d consider myself an intermediate, and I’ve worked with software and developer professionals with decades of experience to integrate wit…

I’m not a programmer by any means, but I understand the basics of a REST API and how it looks and works. The Fibery API is really strangely made, and quite difficult to understand. Aside from that, the docs are indeed a bit of a mess. [image] Chr1sG: have a look here This is not really help…

[image] Nevil_Hulspas: And how does the sidebar help? It’s about all sort of different topics except the API. To be fair, you are looking at the entire publicly shared Fibery workspace, which contains the Roadmap, Fibery Process and Changelog spaces, as well as the User Guide (which is where …

Now that you have explained why it is like it is, it still doesn’t change anything about the fact that it’s unclear documentation for us. So I’m not sure if you guys received the feedback properly. The above explanations doesn’t make it better for the users, so to speak. But it’s not a priority as …

[image] Nevil_Hulspas: it still doesn’t change anything about the fact that it’s unclear documentation for us. So I’m not sure if you guys received the feedback properly Sure, we get that not everyone appreciates the documentation as it is, but I figured it was worth explaining some of the or…

[image] Nevil_Hulspas: So I’m not sure if you guys received the feedback properly Hey Nevil, Your feedback is clear, and we’ve noted it. We’re not skipping over it.

the by far biggest issue with having the documentation of fibery in fibery itself is that no documentation scraper of any ai tool i tried can scrape the documentation. this is pretty important to work around the severe lack of documentation to be honest. i wrote my own scraper tool to scrape the doc…

I’ve run into the same issue. Trying to use Cursor to load the documentation but because how it’s structured it can’t parse. Tried to scrape the API docs and dump it all into a single file but couldn’t make that work either. First time I’ve run into this issue with documentation and see others have …

I saw somewhere here in the community this week that this issue was fixed.

More programmer-friendly API docs

API & Programming

Chr1sG Split this topic January 2, 2025, 10:35am 5

3 posts were split to a new topic: Help with API for views/documents

Topic		Replies	Views
Move Rest API documentation to industry standard application Ideas & Features api	2	80	February 4, 2026
We've moved Fibery API docs into Fibery API & Programming	2	345	December 28, 2024
Any plans on making docs have sub-documents? Ideas & Features	13	1556	December 12, 2020
Host The Fibery Documentation on GitLab/GitHub	2	15	March 19, 2026
Nested Documents feedback (internal wiki, etc) Ideas & Features rich-text	18	839	March 23, 2023

More programmer-friendly API docs

Related topics