Dear SeaTable Community,
We are excited to announce that SeaTable Cloud version 5.3 is just around the corner, with an expected release in mid-June 2025. This update brings two important changes that may affect how you interact with our API.
1. Removal of /dtable-db and /dtable-server endpoints
As previously announced in February 2025 (see details here), the deprecated /dtable-db and /dtable-server API endpoints will be permanently removed in version 5.3.
What does this mean for you?
- All API requests must now use the SeaTable API Gateway.
- If you have developed custom solutions using the SeaTable API, please check your code to ensure you are not relying on the deprecated endpoints.
- No action is required if you are using the latest versions of n8n, Make, Zapier, or standard Python/JavaScript integrations within SeaTable.
2. Introduction of Team API Limits
As first announced in 2024 (see announcement), we will introduce team-based API usage limits with version 5.3.
Why are we making this change?
- This step is necessary to ensure fair and reliable service for all users, as some teams have generated extremely high API traffic that we could not previously limit.
- API limits will be set monthly, based on your subscription level and team size.
- Good news: Over 95% of users will not be affected by these limits. They are designed to impact only teams with exceptionally high API usage.
Rollout plan:
We will monitor actual API usage for 1-2 weeks after release before gradually enforcing the limits, giving everyone time to adapt.
More details about the upcoming release and these changes will follow soon on https://seatable.com, on this forum and via newsletter.
If you have any questions or concerns, please don’t hesitate to reach out here in the forum.
Best regards,
Christoph
