# Contact Batch Upsert Does Add Properties on Newly Created Objects

**URL:** <https://community.hubspot.com/t/contact-batch-upsert-does-add-properties-on-newly-created-objects/122315>\
**Category:** APIs & Integrations\
**Tags:** professional\
**Created:** [December 11, 2024, 2:58pm UTC](https://community.hubspot.com/t/contact-batch-upsert-does-add-properties-on-newly-created-objects/122315 "2024-12-11T14:58:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anya23](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@Anya23](https://community.hubspot.com/u/Anya23)\
**Post date:** [December 11, 2024, 2:58pm UTC](https://community.hubspot.com/t/contact-batch-upsert-does-add-properties-on-newly-created-objects/122315/1 "2024-12-11T14:58:56Z")

</div>

I am using the /crm/v3/objects/contacts/batch/upsert endpoint to test creating and updating contacts. While it seems to update fine, and it does create new contacts, it is not setting the properties on these new contacts. Here’s my JSON body :

{

“inputs”: [

{

“properties”: {

“active”: “false”

},

“id”: “[existing1@gmail.com](mailto:existing1@gmail.com)”,

“idProperty”: “email”

},

{

“properties”: {

“active”: “false”

},

“id”: “[existing2@gmail.com](mailto:existing2@gmail.com)”,

“idProperty”: “email”

},

{

“properties”: {

“active”: “true”,

“firstname”: “Upsert”,

“lastname”: “Test”

},

“id”: “[doesNotExist@gmail.com](mailto:doesNotExist@gmail.com)”,

“idProperty”: “email”

}

]

}

While it will update the active value on the first two, and it will create a contact with an email [doesNotExist@gmail.com,](mailto:doesNotExist@gmail.com,) it doesn’t set active, firstname or lastname. What am I missing?

---

<div class="post-metadata">

**Author:** ![zach\_threadint](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/zach_threadint/32/46318_2.png) [@zach\_threadint](https://community.hubspot.com/u/zach_threadint)\
**Post date:** [December 11, 2024, 8:10pm UTC](https://community.hubspot.com/t/contact-batch-upsert-does-add-properties-on-newly-created-objects/122315/2 "2024-12-11T20:10:09Z")

</div>

Hi @Anya23 👋

I’ve been able to replicate your results and agree this is not consistent with generally accepted expectations for a “batch upsert” API endpoint. I’ve also found [this related post](https://community.hubspot.com/t5/APIs-Integrations/Contact-batch-upsert-endpoint/m-p/1008345) which seems to be consistent with your experience.

It’d be great to get some input from [@Jaycee\_Lewis](https://community.hubspot.com/t5/user/viewprofilepage/user-id/127074) [@BérangèreL](https://community.hubspot.com/t5/user/viewprofilepage/user-id/230185) as to any planned updates to the [CRM \> Contacts \> Create or update a batch of contacts by unique property values](https://developers.hubspot.com/beta-docs/reference/api/crm/objects/contacts#post-%2Fcrm%2Fv3%2Fobjects%2Fcontacts%2Fbatch%2Fupsert) endpoint, because at the moment it seems pretty unusable.

I hope this proves helpful. Please let me know if you have any follow-up questions.

---

<div class="post-metadata">

**Author:** ![Anya23](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@Anya23](https://community.hubspot.com/u/Anya23)\
**Post date:** [December 16, 2024, 12:45pm UTC](https://community.hubspot.com/t/contact-batch-upsert-does-add-properties-on-newly-created-objects/122315/3 "2024-12-16T12:45:04Z")

</div>

Yeah, it’s really strange. I duplicated it over and over, and was perplexed. Then I did it another time, without (I thought) changing anything, and suddenly it started updating. Not sure if some patch was released in the meantime?

---

<div class="post-metadata">

**Author:** ![zach\_threadint](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/zach_threadint/32/46318_2.png) [@zach\_threadint](https://community.hubspot.com/u/zach_threadint)\
**Post date:** [December 17, 2024, 8:43pm UTC](https://community.hubspot.com/t/contact-batch-upsert-does-add-properties-on-newly-created-objects/122315/4 "2024-12-17T20:43:19Z")

</div>

Hi @Anya23 👋

Yes, I agree -- it seems like HubSpot has resolved the issue 🙂