Breaking Changes in thingsHub 7.0
This document outlines the changes that users must be aware of when upgrading from thingsHub 6.0 to thingsHub 7.0:
Introduction of Business Objects
With thingsHub 7.0, we are introducing the concept of Business Objects, which represent key data entities that reflect various aspects of your business operations. This allows users to create and manage custom fields.
The Assets business objects are currently supported.
Understanding the breaking changes in thingsHub 7 requires some familiarity with this concept. The documentation for the Business Objects is available at: Business Objects
Replacing v3/assets
with v4/assets
With ThingsHub 7.0, we have combined the Assets and Tracked Assets lists to a single Assets Inventory, and removed all support for v3/assets…
endpoints, replacing them with the unified v4/assets
endpoints.
The new asset endpoints are compatible with the Business Objects, and support Custom fields of various types.
A summary of the API Changes and newly added v4
endpoints are mentioned in the table below:
Old Endpoint | New Endpoint | Key Changes | Remarks |
---|---|---|---|
GET POST PUT DELETE | GET POST PUT DELETE | Old request and response format:
CODE
New request and response format:
CODE
|
|
GET | GET | Query Parameter Changes to the Listing Endpoints:
Response change: The
CODE
| |
POST | - | This endpoint has been removed | |
DELETE | - | This endpoint has been removed |
Replacing v3/assets-import
endpoint with v4/assets-import
With ThingsHub 7.0, we have replaced the v3/assets-import
with the improved v4/assets-import
endpoint, with Business Objects fields support.
This means that users will now be able to import data into custom fields that they have created as Business Objects.
API users of the v3/assets-import
APIs will have to make the following changes to ensure proper functioning for asset import:
Use the POST
https://{your_tenant_url}/api/v4/assets-import
endpoint instead of thehttps://{your_tenant_url}/api/v3/assets-import
endpoint.If you want to use a key other than
id
,uid
as the ID, or you use a key other thanname
as the Name, you will also need to provide the following query parameters:id_mapping_field
→ The JSON key to use as the IDname_mapping_field
→ The JSON key to use as the Name
For further details on how Asset Import works in thingsHub 7, and the relevant validations that come with this, please consult our official documentation on this: Asset Import in ThingsHub
Deprecation of the v3/tracked-assets
endpoints
As the old Asset Inventory and Tracked Asset inventories have been combined to a single Assets inventory, all the v3/tracked-assets...
endpoints have been deprecated with thingsHub 7.0.
This also means that the canonical way to bind and unbind assets has also changed:
Action | Previously | Now |
---|---|---|
Bind | POST | POST |
Unbind | DELETE | POST |
Please go through the swagger page of your thingsHub tenant for the request and response formats.
Breaking helm changes:
Only for On-Premise Customers
There are no breaking Helm changes coming with thingsHub 7.0.
✅ Required Actions
Users should take the following actions to adjust to these breaking changes:
Update any existing API calls to use the
v3/assets
endpoints tov4/assets
as per the above table.Use the
v4/assets-import
endpoint for importing assets into thingsHub instead of the now removedv3/assets-import
Use the new
/v4/assets/{id}/bind
and/v4/assets/{id}/unbind
endpoints for binding and unbinding assets respectively.