# Vote for the next Public Tulip API

**URL:** <https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822>\
**Category:** Developer\
**Tags:** api, feature-request\
**Created:** [June 24, 2024, 7:28pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822 "2024-06-24T19:28:03Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![danielpomeranz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/danielpomeranz/32/9379_2.png) [@danielpomeranz](https://community.tulip.co/u/danielpomeranz)\
**Post date:** [October 15, 2024, 10:10pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/18 "2024-10-15T22:10:09Z")

</div>

@kevin.kononenko These questions are going to keep coming until Tulip decides if User Custom Fields is a real table or not. Until this is decided I would recommend most people just design an architecture with a normal table for User Custom fields and load the current user by name or by badge ID [“On App Sign In”](https://community.tulip.co/t/triggers-on-sign-in-or-on-player-open/12439).

---

_[View the full topic](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822)._