# Change in API error responses

**URL:** <https://community.hubspot.com/t/change-in-api-error-responses/14132>\
**Category:** APIs & Integrations\
**Tags:** companies, developer-tools, object\
**Created:** [April 26, 2019, 10:06am UTC](https://community.hubspot.com/t/change-in-api-error-responses/14132 "2019-04-26T10:06:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![benc-bright](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/benc-bright/32/9140_2.png) [@benc-bright](https://community.hubspot.com/u/benc-bright)\
**Post date:** [April 26, 2019, 10:06am UTC](https://community.hubspot.com/t/change-in-api-error-responses/14132/1 "2019-04-26T10:06:11Z")

</div>

I’ve got a HubSpot API integration that has recently run into a few issues. The integration is built to expect occasional errors to be returned from the API, and knows how to handle and log these. The errors are expected to be in the JSON format documented at [Accounts Dashboard | HubSpot](https://developers.hubspot.com/docs/faq/api-error-responses).

However, in the last few days the error responses seem to be in a different format, and don’t include the _requestId._ This is causing the errors to propagate through my application, as the error response deserialization fails due to the missing field. This field is being excluded across multiple endpoints, so seems to have been removed from the error response format - the below screenshot is from a POST request to the Deals API (deals/v1/deal/):

 ![Screen Shot 2019-04-25 at 14.23.56.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/a/8/a8848f2e056642dcd2110a5be505bb677a2f26eb.png)

Is this a known change to how the API works? I can’t find it anywhere in the changelog, and am hesitant to change my integration if the _requestId_ is going to be reinstated.

---

<div class="post-metadata">

**Author:** ![cbarley](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cbarley/32/82559_2.png) [@cbarley](https://community.hubspot.com/u/cbarley)\
**Post date:** [April 29, 2019, 3:57pm UTC](https://community.hubspot.com/t/change-in-api-error-responses/14132/2 "2019-04-29T15:57:40Z")

</div>

Hi @benc-bright, I’ve been talking with Lisa, the support rep you’ve been working with, about this. It looks like this format did actually change unexpectedly recently. Engineering is now looking into the issue and we’ll get back to you soon. I’ll post here retroactively, but for the swiftest support, reaching out to Lisa will be your best bet, instead of pinging this thread. Thanks @benc-bright and thanks for letting us know!

---

<div class="post-metadata">

**Author:** ![cbarley](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cbarley/32/82559_2.png) [@cbarley](https://community.hubspot.com/u/cbarley)\
**Post date:** [April 30, 2019, 6:59pm UTC](https://community.hubspot.com/t/change-in-api-error-responses/14132/3 "2019-04-30T18:59:02Z")

</div>

hi @benc-bright , we’ve resolved this issue. This was not supposed to occur, so you can certainly expect those to be present in the response. We may move to a more useful format without **correlationId** and **requestId** in a future world, but you should expect any changes will be posted in the changelog: [HubSpot Developer Changelog](https://developers.hubspot.com/changelog), and a minimum of 90 days heads up. Sorry for the confusion here!

---

<div class="post-metadata">

**Author:** ![benc-bright](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/benc-bright/32/9140_2.png) [@benc-bright](https://community.hubspot.com/u/benc-bright)\
**Post date:** [May 1, 2019, 7:20am UTC](https://community.hubspot.com/t/change-in-api-error-responses/14132/4 "2019-05-01T07:20:18Z")

</div>

Hi @cbarley, thanks for the update and for fixing the issue. I’ll keep an eye on the changelog for any future updates regarding the removal of these fields.