Create unique identifier for Contact

Developer Support APIs & Integrations
1

Hi everyone!
I’m trying to create a unique property via the API on the Contact object. The property is being created, but the hasUniqueValue property is being set to false despite explicitly setting it to true in the request.
This post announces that support for Contacts has been rolled out so perhaps I’m making a mistake in my request, or there is some config in the UI I forgot to toggle maybe? (I am able to make it work for Company objects as a sanity check)

testUniqueProperty.png
testUniqueProperty.png1439×886 132 KB

Postman example

2

i am facing the same issue

3

680×360 101 KB
Api call request and response .
I am facing the same issue , I am trying the same from 2 days , i was also thinking the same way , that may be i am makign some mistake ,
I will urge hubspot team to give response on this as soon as possible .
Thanking you in advance .

4

AHussain17_0-1703152685252.png
AHussain17_0-1703152685252.png1754×855 270 KB

Issue :- Unique property creation in contact
Although unique properties creation working by from UI of hubspot , not working the same by api call , that we made from node.js api client or hubspot developer api .

5

Hi Everyone,
This is a known bug that the HubSpot engineering team are currently triaging.
Once a fix has been deployed I will update the post to let you all know.
Thank you for your continued patience.

6

Thanks for giving response on this .
we just want to know if there is any deadline to fix this issue .

7

Hi,
The engineering team are currently triaging the bug, they’ll then need to deploy a solution. As soon as the team have shared an update I can provide a more accurate time to solution. As mentioned I will update the post when I have more information from the engineering team.
Thank you for your continued patience.

8

Hello everyone,
The HubSpot engineering team have just deployed a fix for this bug. The public CRM properties API can now create unique identifier properties for contacts once again.
Thank you all for your patience while we resolved this bug.