SeaTable 4.4 out now!

Dear @siax84,

thanks for feedback. With 4.4 we introduced the so-called API gateway, which will allow us to implement API limits in the future. I already wrote about this in the past: https://forum2.seatable.io/t/updates-to-our-subscriptions-introducing-team-api-limits/3265

In addition, the API gateway also harmonizes and improves all dtable-db and dtable-server endpoints. But all former endpoints stay alive and can still be used. Look at our API documentation at https://api.seatable.io, you will find all new and former endpoints.

Long story short:

  • if you observe changes in the output, please return to us. This should not be the case and we will fix this.
  • you don’t have to switch to the new API endpoints. The old endpoints are still valid.
  • some clients require an additional parameter to follow the redirect. In case of curl, you have to add -L to the command.
1 Like