# Changing from POST to PATCH

**URL:** <https://community.hubspot.com/t/changing-from-post-to-patch/144700>\
**Category:** APIs & Integrations\
**Tags:** object, contacts\
**Created:** [January 8, 2026, 1:28pm UTC](https://community.hubspot.com/t/changing-from-post-to-patch/144700 "2026-01-08T13:28:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Victor\_Becerra](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@Victor\_Becerra](https://community.hubspot.com/u/Victor_Becerra)\
**Post date:** [January 8, 2026, 4:12pm UTC](https://community.hubspot.com/t/changing-from-post-to-patch/144700/2 "2026-01-08T16:12:54Z")

</div>

Hi there @HDilloway

Thanks for reaching out — I can see why this is urgent if leads are getting dropped when a contact already exists.

I’d like to invite some community members who are subject matter experts in HubSpot APIs and contact upserts to join this conversation.  
@BrandonWoodruff @evaldas @kosalaindrasiri — hope you’re all having a great week! Can you share the best-practice way to change a create-only flow (POST) into an update-or-create pattern (PATCH/upsert) for contacts, and what endpoints/payload structure they should use to avoid duplicates and failed lead creation?

Any guidance would be greatly appreciated.  
Best,  
Victor

---

_[View the full topic](https://community.hubspot.com/t/changing-from-post-to-patch/144700)._
