topic Re: Hubspot HubDB API issue in APIs & Integrations

Hubspot HubDB API issue

AJohnson94 — Thu, 15 Jun 2023 14:34:18 GMT

Hi,

I have encounted an issue with the Hubspot API.

Endpoint: https://api.hubapi.com/cms/v3/hubdb/tables/4980460/rows/draft/batch/create

When creating rows that contain column types of ForeignID, or SELECT, we pass the values in as an object e.g.:

"translations": [ { "id": "71643448559", "type": "foreignid" }, { "id": "71643448561", "type": "foreignid" } ],

This works fine. Before today, the response also contained the values in the same format.

Today however, the response is coming back as:

"translations": ",71643448559,71643448561,71643448563,",

This is breaking the code that parses into a model, as it's a string rather than an object.

I can't find any documented changes in the developer changelog so this feels more like a bug to me.

I can change the response model to work with the string that is coming back, but I don't want to do that in case it is a bug and it changes back to returning an object.

Could someone from Hubspot please advise?

Thanks

Re: Hubspot HubDB API issue

Jaycee_Lewis — Fri, 16 Jun 2023 23:08:42 GMT

Hi, @AJohnson94 👋 This does sound unexpected. One question — have you already filed a support ticket for this issue?

Thanks for the additional info. — Jaycee

Re: Hubspot HubDB API issue

AJohnson94 — Mon, 19 Jun 2023 07:42:41 GMT

Hi @Jaycee_Lewis I spoke to someone on support and they recommended I post here.

It would be useful to get a response from a Hubspot developer who can shed some light on this as it's impacting a project for a client and we're unsure of how to proceed. Thanks

Re: Hubspot HubDB API issue

wspiro — Mon, 28 Aug 2023 14:03:16 GMT

Hi all,

Sorry for just seeing this post now. This was a bug that we actually fixed back on July 10th. Is anyone still having issues? For posterity, HubSpot Support is the best place to report bugs of this nature (it sounds like you actually did create a Support issue and they referred you here, but I just wanted to note that Support was the best route to get a bug addressed).