# Errorcode details

**URL:** https://community.baserow.io/t/errorcode-details/9764
**Category:** Baserow Academy
**Created:** [March 22, 2025, 7:41am UTC](https://community.baserow.io/t/errorcode-details/9764 "2025-03-22T07:41:21Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![360Creators](https://community.baserow.io/user_avatar/community.baserow.io/360creators/32/3827_2.png) [@360Creators](https://community.baserow.io/u/360Creators)
#### Post date: [March 22, 2025, 7:41am UTC](https://community.baserow.io/t/errorcode-details/9764/1 "2025-03-22T07:41:21Z")

</div>

Hey hey,

As I was going through the expert course, I wondered why the “details” don’t show up in the errorcode directly instead of going to dev tools \> network? Happy to have learned this anyway, just curiousity.

---

<div class="post-metadata">

### Author: ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)
#### Post date: [March 25, 2025, 12:08pm UTC](https://community.baserow.io/t/errorcode-details/9764/2 "2025-03-25T12:08:11Z")

</div>

Hey @360Creators, it might be a good idea to show the human-readable API errors directly in the frontend if there is no mapping available.

In most cases, there is a mapping in the frontend that links the error code to a translatable human-readable error that less technical compared to the API one. But in case there is no mapping, we could just show the more technical error in English. That might help the user.

---

<div class="post-metadata">

### Author: ![360Creators](https://community.baserow.io/user_avatar/community.baserow.io/360creators/32/3827_2.png) [@360Creators](https://community.baserow.io/u/360Creators)
#### Post date: [March 25, 2025, 12:47pm UTC](https://community.baserow.io/t/errorcode-details/9764/3 "2025-03-25T12:47:01Z")

</div>

Yes that’d be better! Thank you!
