HubDB v3 API now in General Availability (GA)

[AJLaPorte]

Today we are excited to announce that we are releasing our HubDB V3 API into General Availability (GA) as part of our ongoing effort to improve the consistency and completeness of our developer APIs.

What's changing?

The following are changes in v3 of the HubDB API:

• Tables should have both name and label. This name cannot be changed once the table is created. Names can only include lowercase letters, digits, and underscores and cannot begin with a number. Both name and label should be unique in the account.
• API supports both table id and name in the URL paths.
• GET row endpoints return column name instead of id in values field. Also, POST / PUT / PATCH row endpoints require column name instead of id in values field.
• Row update PATCH endpoints now accept sparse updates, which means you can specify only the column values that you need to update (whereas we had to specify all the column values in the previous versions). When you update a column with a list of values such as multi-select, you need to specify the list of all the values. In order to delete the value for a column, you need to specify the column with the value as null in the request.
• Removed the endpoints to GET / UPDATE / DELETE a row cell in favor of the row update PATCH endpoints.
• Import endpoint now supports an optional field idSourceColumn along with existing fields in the JSON-formatted options. You can use this field to specify the column in the csv file which contains row ids. To import new rows along with the new values for existing rows, you can specify 0 as the row id for the new rows and the valid row ids for the existing columns. See more details in the Import section below. Also you can use column names or ids in the target field of the column mappings in the JSON-formatted options.
• Clone endpoint requires a new name and new label.

If you have any questions or comments, please feel free to leave a message below.