# idProperty=email continued support?

**URL:** <https://community.hubspot.com/t/idproperty-email-continued-support/104162>\
**Category:** APIs & Integrations\
**Tags:** email, oauth, contacts\
**Created:** [April 4, 2024, 8:09pm UTC](https://community.hubspot.com/t/idproperty-email-continued-support/104162 "2024-04-04T20:09:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JHutcheson](https://avatars.discourse-cdn.com/v4/letter/j/ecccb3/32.png) [@JHutcheson](https://community.hubspot.com/u/JHutcheson)\
**Post date:** [April 4, 2024, 8:09pm UTC](https://community.hubspot.com/t/idproperty-email-continued-support/104162/1 "2024-04-04T20:09:40Z")

</div>

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:

> **[Accounts Dashboard | HubSpot](https://app.hubspot.com/myaccounts?next=developerdocs&redirect=%2Fapi-reference%2Fcrm-contacts-v3%2Fguide)**

Is this kind of filter going to continue to be supported, or is there another way to acheive this thats better documented/supported?

---

<div class="post-metadata">

**Author:** ![Teun](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/teun/32/28739_2.png) [@Teun](https://community.hubspot.com/u/Teun)\
**Post date:** [April 5, 2024, 8:43pm UTC](https://community.hubspot.com/t/idproperty-email-continued-support/104162/2 "2024-04-05T20:43:52Z")

</div>

Hi @JHutcheson ,

I agree that it isn’t documented that well, however, it is still mentioned as a valid method in the [docs](https://developers.hubspot.com/docs/api/crm/contacts#update-contacts).  
So because of that, I think you can safely use this approach.

---

<div class="post-metadata">

**Author:** ![ericbn](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@ericbn](https://community.hubspot.com/u/ericbn)\
**Post date:** [September 23, 2025, 5:42pm UTC](https://community.hubspot.com/t/idproperty-email-continued-support/104162/3 "2025-09-23T17:42:38Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![chighsmith](https://avatars.discourse-cdn.com/v4/letter/c/77aa72/32.png) [@chighsmith](https://community.hubspot.com/u/chighsmith)\
**Post date:** [September 23, 2025, 6:29pm UTC](https://community.hubspot.com/t/idproperty-email-continued-support/104162/4 "2025-09-23T18:29:13Z")

</div>

Hi @ericbn,  
Thank you for posting to the Community!  
I was able to find this [similar thread](https://community.hubspot.com/t5/APIs-Integrations/Update-contact-with-email-as-ID-through-the-Hubspot-API/m-p/623680) 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

---

<div class="post-metadata">

**Author:** ![ericbn](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@ericbn](https://community.hubspot.com/u/ericbn)\
**Post date:** [September 23, 2025, 8:02pm UTC](https://community.hubspot.com/t/idproperty-email-continued-support/104162/5 "2025-09-23T20:02:48Z")

</div>

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.