Improve API batch errors

[Sachavskyi]

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 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",
        ....
    }
]

[wtx-signalfire]

I am also in favor of this proposal

[OGrigorov]

Agreed. This is an annoying problem causing a lot of issues for customers using our Hubspot integration

[Shriki]

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! 

[RdotCosta]

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?