APIs & Integrations

alpipego
Member

Custom Property can't be populated via API

Actually this is a re-post of a comment I made on a similar topic: Custom properties and API Since I got no answer there, I though I’ll try to open a new ticket.

I have added a custom property to our account and I can use it just fine from the backend but whenever I want to populate the field via an API call I get the error PROPERTY_DOESNT_EXIST.

{
  "status": "error",
  "message": "Property values were not valid",
  "correlationId": "xxxx",
  "validationResults": [
    {
      "isValid": false,
      "message": "Property \"heins\" does not exist",
      "error": "PROPERTY_DOESNT_EXIST",
      "name": "heins"
    }
  ],
  "requestId": "e971121a421508d9792499ecc75c662f"
}

Thanks in advance.
Alex

0 Upvotes
6 Replies 6
Not applicable

Custom Property can't be populated via API

I’m having the same problem. Has this been resolved yet?

0 Upvotes
3PETE
HubSpot Employee
HubSpot Employee

Custom Property can't be populated via API

@jideokus I’ll DM you to grab your portal info. That isn’t an expected outcome.

3PETE
HubSpot Employee
HubSpot Employee

Custom Property can't be populated via API

@alpipego

Can you show me the full request you are making to HubSpot?

0 Upvotes
alpipego
Member

Custom Property can't be populated via API

POST /contacts/v1/contact/?hapikey=XXXXXXX HTTP/1.1
Host: api.hubapi.com
Content-Type: application/json
Cache-Control: no-cache
Postman-Token: e13b7771-10cc-3409-fde9-cc8b3a91deb0

{
	"properties": [
		{
			"property": "email", 
			"value": "alpipego@test.com"
		},
		{
			"property": "heins",
			"value": "heins6"
		}
	]
}
0 Upvotes
3PETE
HubSpot Employee
HubSpot Employee

Custom Property can't be populated via API

@alpipego Just out of curiosity how recently did you make that property? It should be almost instantaneous but some times it can take an hour or two to take affect on the entire back end if our servers our back logged.

0 Upvotes
alpipego
Member

Custom Property can't be populated via API

Since my original post is more than two weeks old, the property is even a bit older. :wink:

0 Upvotes