On Jan 31, 2024, we will be sunsetting the following items in relation to HubDB:
We encourage users to migrate the HubDB v3 API. This API includes many performance, usability, and API consistency improvements over the v1 and v2 API. This includes:
- Tables are required to have both a
- Support for both table
namein the url paths.
GETrow endpoints return column
idin the values field. Also,
PATCHrow endpoints require column
- Row update
PATCHendpoints now accept sparse updates, which allows you to specify only the column values that you need to update, unlike the previous version where you had to specify all the column values.
- Removed the
DELETEendpoints for a single cell in a row in favor of the row update
- Import endpoint now supports an optional field
idSourceColumnto make it easier to update existing rows, along with existing fields in the JSON-formatted options.
- Clone endpoint requires a new
Read more about our HubDB v3 API, view examples, and begin planning your migration to the new version.
Discuss this change on our community post here.