Currently our app depends on an http request to this URI:
PATCH /crm/v3/objects/contacts/[EMAIL]?idProperty=email
This seems to work at the moment. However, this style of upsert using the email as the id and idProperty=email as a query param doesnt seem to be visible in any of the docs for the contact object:
Is this kind of filter going to continue to be supported, or is there another way to acheive this thats better documented/supported?
Hi @JHutcheson ,
I agree that it isn’t documented that well, however, it is still mentioned as a valid method in the docs.
So because of that, I think you can safely use this approach.
This started failing with 404 Not Found and response with message: “Object not found. objectId are usually numeric.” for us, even when a contact with the given email exists. In this something that needs to be fixed on the Hubspot side?
Hi @ericbn,
Thank you for posting to the Community!
I was able to find this similar thread with an Accepted Solution that you may find useful. I’d also, like to tag in some of our Top Contributors to see if they have experienced this error before.
Hi @WesQ @Bortami and @Teun Have any of you all seen the “Object not found. objectId are usually numeric.” error before? If so, how were you able to resolve it?
Thank you!
Cassie, Community Manager
I see the issue is fixed now. We didn’t change anything on our side, so it looks like this was a failure on Hubspot. As far as we’ve observed, this lasted from 11:00 AM to 1:30 PM CDT today.