# API Guide improvements: add images related to Fibery UI **URL:** \ **Category:** Ideas & Features\ **Created:** [August 28, 2025, 9:45pm UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493 "2025-08-28T21:45:56Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [August 28, 2025, 9:45pm UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493/1 "2025-08-28T21:45:57Z")
“A picture is worth a 1000 words”. I’m now trying to hack my understanding of API to update data in my workspace via n8n. What would ease is having some images to visually connect API-based data structures to their respective entities & fields in Fibery UI. The logic of query structures reminds me SQL. But currently I have to make quite some effort to understand new structures given it’s not a typical API I’m used to + I face some errors. 🙂 ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 29, 2025, 6:08am UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493/2 "2025-08-29T06:08:20Z")
Can you upload a simple sketch of what you think a useful image would be. I’m struggling to visualise something that would clarify what is essentially a very code-heavy topic to talk about. ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [August 29, 2025, 6:58am UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493/3 "2025-08-29T06:58:50Z")
[API Query error entity.error/schema-field-not-found - #2 by Chr1sG](https://community.fibery.io/t/api-query-error-entity-error-schema-field-not-found/9494/2) - typical example trying to understand how field names in API corelate to the field names in Fibery. It was an “unclear & surprising discovery” that I should use spaceName/fieldName notation to refer to fields in API. My initial thought was it should have been something like tableName/fieldName instead. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 29, 2025, 7:01am UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493/4 "2025-08-29T07:01:49Z")
Is there an example of an image that might have accelerated this discovery for you? ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [August 29, 2025, 7:02am UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493/5 "2025-08-29T07:02:29Z")
Ok, will do later today ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [August 29, 2025, 2:14pm UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493/6 "2025-08-29T14:14:12Z")
Basically, when I was studying the Entity API reference I got confused with “Cricket/Player“ sample. Don’t ask me why. 🙂 Something didn’t click there. Perhaps, for me personally I’d rather prefer something like “Company/Employee“ or “Folder/File“ or “CRM/Person“ instead. Since this is not a straightforward REST API, it takes quite some time with trial & errors, especially at the beginning to making the connections between the entities & their properties on the API level and the actual workspace I have in place. Therefore, visualization could ease getting started. So, I’d love see how this: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d581c384c54271282ecb1fdfd0fcc50caa62a658.png) would map to this: ```auto curl -X POST https://YOUR_ACCOUNT.fibery.io/api/commands \ -H 'Authorization: Token YOUR_TOKEN' \ -H 'Content-Type: application/json' \ -d \ '[ { "command": "fibery.entity/query", "args": { "query": { "q/from": "Cricket/Player", "q/select": [ "fibery/id", "fibery/public-id", "Cricket/name", "Cricket/Full Name", "Cricket/Born", "Cricket/Shirt Number", "Cricket/Height", "Cricket/Retired?", { "Cricket/Batting Hand": ["enum/name"] }, { "Cricket/Current Team": ["Cricket/name"] }, { "user/Former Teams": { "q/select": ["Cricket/name"], "q/limit": "q/no-limit" } }, { "# of former teams": ["q/count", ["user/Former Teams", "fibery/id"] ] } ], "q/where": [">=", ["Cricket/Born"], "$birthday" ], "q/order-by": [ [["Cricket/Height"], "q/desc"], [["Cricket/Born"], "q/asc"] ], "q/limit": 3 }, "params": { "$birthday": "1986-01-01" } } } ]' ``` Now, I understand the notation a bit more. What’s confusing though is things like: ```auto "Cricket/name", "Cricket/Full Name", ``` In my head name and Full Name belong to the table (Player) - not the database (Cricket). What if we have a table Referee with similar fields like name and Full Name? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 29, 2025, 2:37pm UTC](https://community.fibery.io/t/api-guide-improvements-add-images-related-to-fibery-ui/9493/7 "2025-08-29T14:37:59Z")
> [@myg\_ge](#): > > In my head name and Full Name belong to the table (Player) - not the database (Cricket). What if we have a table Referee with similar fields like name and Full Name? I think the terminology is wrong here I’m afraid (at least, using [Fibery terms](https://the.fibery.io/@public/User_Guide/Guide/Fibery-Glossary-403)) In the API example, `Cricket` is the **space name** , and within the `Player` database there is a field, whose title is `Name`, but whose name (according to the API) is `Cricket/name`. There indeed could be another database called `Referee` which also has a field whose title is `Name`, but whose name (according to the API) is `Cricket/name`. However, since an entity query is always made to a single database (using `"q/from": "/"`) there is no chance of these fields being mistaken for each other.