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!
Analytics API: an API to create, edit, and export Analytics
Apps API: an API to configure Apps at scale, as well as perform CRUD operations on Apps
Automations API: an API to configure and trigger Automations remotely
Completions API: an API to read, update, and delete App Completions
Library API: an API to create, edit, and delete Libraries across Instances and Workspaces
Site Configuration API: a set of APIs to configure settings for an Instance of Tulip
Users API: an API to configure Users on an instance of Tulip
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
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.
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
If you enjoy this, or have other endpoints you are looking for, let us know in the comments here!
@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”.
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).