Upcoming Sunset: HubDB v1 API, HubDB v2 API, and HubDB JavaScript Client
On Jan 31, 2024, we will be sunsetting the following items in relation to HubDB:
- HubDB API v1
- HubDB API v2
- HubDB JavaScript Client
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
name
andlabel
. - Support for both table
id
andname
in the url paths. GET
row endpoints return columnname
instead ofid
in the values field. Also,POST
,PUT
, andPATCH
row endpoints require columnname
instead ofid
invalues
field.- Row update
PATCH
endpoints 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
GET
,UPDATE
, andDELETE
endpoints for a single cell in a row in favor of the row updatePATCH
endpoints. - Import endpoint now supports an optional field
idSourceColumn
to make it easier to update existing rows, along with existing fields in the JSON-formatted options. - Clone endpoint requires a new
name
and newlabel
.
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.