# Improve API batch errors **URL:** \ **Category:** HubSpot Ideas\ **Tags:** help-desk, api, object\ **Created:** [June 26, 2024, 7:27am UTC](https://community.hubspot.com/t/improve-api-batch-errors/110135 "2024-06-26T07:27:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Sachavskyi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sachavskyi/32/39641_2.png) [@Sachavskyi](https://community.hubspot.com/u/Sachavskyi)\ **Post date:** [June 26, 2024, 7:27am UTC](https://community.hubspot.com/t/improve-api-batch-errors/110135/1 "2024-06-26T07:27:21Z")
I’m trying to use HubSpot batch API and have the next problem: when I send 3 contacts to [https://api.hubapi.com/crm/v3/objects/contact/batch/create](https://api.hubapi.com/crm/v3/objects/contact/batch/create) and if one of these contacts has a problem - HubSpot response format is like this: `{ "status": "error", "message": "Property values were not valid: ......." "correlationId": "2c2b03e3-5692-4261-b462-0bea1952e562", "category": "VALIDATION_ERROR"}` Why the response format is not like this: `[{ "status": "error", .... }, { "id": "4136413868", .... }, { "id": "4136413870", .... }]` ---
**Author:** ![wtx-signalfire](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wtx-signalfire/32/203176_2.png) [@wtx-signalfire](https://community.hubspot.com/u/wtx-signalfire)\ **Post date:** [July 8, 2024, 10:17pm UTC](https://community.hubspot.com/t/improve-api-batch-errors/110135/2 "2024-07-08T22:17:19Z")
I am also in favor of this proposal ---
**Author:** ![OGrigorov](https://avatars.discourse-cdn.com/v4/letter/o/dbc845/32.png) [@OGrigorov](https://community.hubspot.com/u/OGrigorov)\ **Post date:** [August 16, 2024, 8:10am UTC](https://community.hubspot.com/t/improve-api-batch-errors/110135/3 "2024-08-16T08:10:56Z")
Agreed. This is an annoying problem causing a lot of issues for customers using our Hubspot integration ---
**Author:** ![Shriki](https://avatars.discourse-cdn.com/v4/letter/s/3ab097/32.png) [@Shriki](https://community.hubspot.com/u/Shriki)\ **Post date:** [September 1, 2024, 1:31am UTC](https://community.hubspot.com/t/improve-api-batch-errors/110135/4 "2024-09-01T01:31:33Z")
The current API is very problematic. You should support a simple batch upsert operation. Requiring to go over all the batch items and check if they exist or not is super inefficient! ---
**Author:** ![RdotCosta](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@RdotCosta](https://community.hubspot.com/u/RdotCosta)\ **Post date:** [October 17, 2024, 6:47pm UTC](https://community.hubspot.com/t/improve-api-batch-errors/110135/5 "2024-10-17T18:47:05Z")
Same problems here. We have escalated shared customer cases where emails were deemed invalid in a batch (to note, these were actual emails) and all records in the batch fail despite the one bad email. This then seems like a failure of our integration product, when it seems like there should be better handling on invalid emails to not error all in the batch. When pointed to HubSpot support about this, our shared customers are then being directed back to us. The loop continues. We’re hesitant to develop around this issue because if you do ever make changes to improve this then it could impact the workaround we’ve made. What can we do here as your partner to improve this experience for our shared Enterprise customers? ---
**Author:** ![SAMsan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/samsan/32/17908_2.png) [@SAMsan](https://community.hubspot.com/u/SAMsan)\ **Post date:** [May 20, 2025, 10:34am UTC](https://community.hubspot.com/t/improve-api-batch-errors/110135/6 "2025-05-20T10:34:41Z")
So bad we had to upvote for an idea (thank you @Sachavskyi) as this should be a bug fixed for years (referring to [this article](https://developers.hubspot.com/changelog/simplifying-batch-update-response-codes-for-crm-v3-apis)).