# 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:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![joshuarichard](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/joshuarichard/32/299_2.png) [@joshuarichard](https://community.tulip.co/u/joshuarichard)\
**Post date:** [June 24, 2024, 7:28pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/1 "2024-06-24T19:28:03Z")

</div>

Hey everyone! My name is Josh and an employee at Tulip. I’m a long-time listener, first-time poster. I want to know which of the following potential new APIs you as a user would find the most valuable. You can select up to three and if you don’t see the one you have in mind listed below then please post it in the comments!

Thanks and happy building!

_Poll ([view on site](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/1))_

---

<div class="post-metadata">

**Author:** ![Beth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/beth/32/5987_2.png) [@Beth](https://community.tulip.co/u/Beth)\
**Post date:** [June 25, 2024, 8:18am UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/6 "2024-06-25T08:18:03Z")

</div>



---

<div class="post-metadata">

**Author:** ![JesseAlbritton](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@JesseAlbritton](https://community.tulip.co/u/JesseAlbritton)\
**Post date:** [June 28, 2024, 11:36am UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/7 "2024-06-28T11:36:20Z")

</div>

Other API: an API to configure machines and machine attributes to reduce implementation time and provides a mechanism to ensure automation system configurations are staying in sync with Tulip machines

---

<div class="post-metadata">

**Author:** ![klickal](https://avatars.discourse-cdn.com/v4/letter/k/a88e57/32.png) [@klickal](https://community.tulip.co/u/klickal)\
**Post date:** [June 28, 2024, 2:10pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/8 "2024-06-28T14:10:46Z")

</div>

100% 🙌 Highly support this one too!

---

<div class="post-metadata">

**Author:** ![joseph.dooher](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@joseph.dooher](https://community.tulip.co/u/joseph.dooher)\
**Post date:** [June 28, 2024, 2:17pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/9 "2024-06-28T14:17:19Z")

</div>

I agree with Jesse, this could be a real game changer for scaling

---

<div class="post-metadata">

**Author:** ![youri.regnaud](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/youri.regnaud/32/2917_2.png) [@youri.regnaud](https://community.tulip.co/u/youri.regnaud)\
**Post date:** [June 29, 2024, 5:35pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/10 "2024-06-29T17:35:35Z")

</div>

Oh yes! Machines Types, Machines, Machines mapping and attributes.

---

<div class="post-metadata">

**Author:** ![paul.genoud](https://avatars.discourse-cdn.com/v4/letter/p/f14d63/32.png) [@paul.genoud](https://community.tulip.co/u/paul.genoud)\
**Post date:** [July 7, 2024, 10:15am UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/11 "2024-07-07T10:15:42Z")

</div>

An API to set downtime reasons for machines ?

---

<div class="post-metadata">

**Author:** ![Nicolas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/nicolas/32/3349_2.png) [@Nicolas](https://community.tulip.co/u/Nicolas)\
**Post date:** [July 19, 2024, 2:15pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/12 "2024-07-19T14:15:35Z")

</div>

An API to read, edit Machine Activity - to be able Status and Downtime reasons in the past.

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [August 23, 2024, 12:58pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/13 "2024-08-23T12:58:32Z")

</div>

Hello all! I have been reaching out to people that requested the Users API. We first plan on releasing GET and LIST endpoints for Users in the next 1-2 months.

Are there other capabilities that you are excited about? Let me know here and I am happy to discuss further.

---

<div class="post-metadata">

**Author:** ![Beth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/beth/32/5987_2.png) [@Beth](https://community.tulip.co/u/Beth)\
**Post date:** [September 3, 2024, 3:05pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/14 "2024-09-03T15:05:05Z")

</div>



---

<div class="post-metadata">

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

</div>

Hi all! As part of the launch for Ops Calling 2024, we did indeed launch a Users API with GET and LIST endpoints. It comes with r289 and later. See our API docs here: [/api/users/v1/users - users](https://support.tulip.co/apidocs/apiusersv1users)

If you enjoy this, or have other endpoints you are looking for, let us know in the comments here!

---

<div class="post-metadata">

**Author:** ![jjj](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/jjj/32/4542_2.png) [@jjj](https://community.tulip.co/u/jjj)\
**Post date:** [October 15, 2024, 6:21pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/16 "2024-10-15T18:21:20Z")

</div>

Will you eventually be able to get the custom fields information for users via API?

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [October 15, 2024, 6:33pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/17 "2024-10-15T18:33:06Z")

</div>

We could certainly do it in future! Why do you want to get info out of User Fields? I am wondering if there is another way to do that as well.

---

<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).

---

<div class="post-metadata">

**Author:** ![mpreiksaitis](https://avatars.discourse-cdn.com/v4/letter/m/8dc957/32.png) [@mpreiksaitis](https://community.tulip.co/u/mpreiksaitis)\
**Post date:** [October 30, 2024, 5:01pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/19 "2024-10-30T17:01:25Z")

</div>

I would vote for more capacity on the existing APIs rather than new development. Specifically for api/v3/tables/[TABLE\_UNIQUE\_ID]/records

The limit of 100 is much smaller than other APIs that we use. Increasing that limit would help.

We have found it is impractical to pull larger tables (or externally sync larger tables) using the API. If you want to follow one of the integration guides that pull data using the API - you better be prepared to wait a week (1M to 10M records).

Ex. [Microsoft Azure Machine Learning Integration](https://support.tulip.co/docs/microsoft-azure-machine-learning-integration) or [Snowflake Integration with Fabric - Fetch Tulip Tables to Snowflake](https://support.tulip.co/docs/snowflake-integration-with-fabric-fetch-tulip-tables-to-snowflake)

---

<div class="post-metadata">

**Author:** ![mellerbeck](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@mellerbeck](https://community.tulip.co/u/mellerbeck)\
**Post date:** [February 14, 2025, 12:38am UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/20 "2025-02-14T00:38:20Z")

</div>

Update multiple rows of data with one API call 🙂

---

<div class="post-metadata">

**Author:** ![ta-aoki](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@ta-aoki](https://community.tulip.co/u/ta-aoki)\
**Post date:** [March 27, 2025, 7:15am UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/21 "2025-03-27T07:15:14Z")

</div>

API to query whether the specific Connector is online or not

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [March 27, 2025, 1:43pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/22 "2025-03-27T13:43:20Z")

</div>

Actually

- {instance}/api/connectors/v1/w/1/connectors?archived=false&offset=0&limit=25

would provide the connectors list and

- {instance}/api/connectors/v1/w/1/connectors/online-status?connectorIds=[`list of connector id's`]

would provide the online status…

unfortunately I think there is no API token you could create yourself to call them successfully…

So this could actually be a quick win for tulip…

---

<div class="post-metadata">

**Author:** ![ta-aoki](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@ta-aoki](https://community.tulip.co/u/ta-aoki)\
**Post date:** [March 28, 2025, 1:08am UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/23 "2025-03-28T01:08:51Z")

</div>

Thank you!  
Yes, I actually saw that API used in the page, but I want officially supported API for the user.

---

<div class="post-metadata">

**Author:** ![AlexOliveros](https://avatars.discourse-cdn.com/v4/letter/a/a698b9/32.png) [@AlexOliveros](https://community.tulip.co/u/AlexOliveros)\
**Post date:** [May 14, 2025, 3:21pm UTC](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822/24 "2025-05-14T15:21:51Z")

</div>

Yes, mass update/create records API. We need this! so far, the only solution I can find is related to loops or automations.

[Next page](https://community.tulip.co/t/vote-for-the-next-public-tulip-api/11822.md?page=2)
