Vote for the next Public Tulip API

Second this suggestion!

Yes and yes. Mass insert/update is a much needed feature that will speed up a lot of our data ingestions. Both looper and automation have their own limitations.

Not sure if it is still the right place to post API feature request.

Today we would like monitor Apps life cyle (what is have been created, when, by who, publish, version) and document an external library of all our apps from different workspace with key information (business description, personas, business process, external apps id from architecture system MegaHopex, list of integration, number of active operator, number of completion).
To do so, we extract with Tulip Apps API the list of apps.
We would like to enhance this api /appGroups with the following information:

  • Apps description
  • Create by and date
  • Change by and date
  • Publish by and date
  • Publih last version

Thanks

2 Likes

Other API: an API to pull full accurate copy of data down to a local source. This would need to have ways to filter based on last update date to only get records that have changed. The end goal is to have data integrity at local database level. New columns added does add complexity to this, as the receiving local data source would need to handle new fields as soon as they are added among other considerations.

Right now it is possible to query for data; but it is a very complex and overwhelming amount of work simply to have a copy of our own data.

Thank you for your consideration ~Steffanie