# Cannot Populate Custom Contact Properties Using A POST API Request (but can using PATCH)

**URL:** <https://community.hubspot.com/t/cannot-populate-custom-contact-properties-using-a-post-api-request-but-can-using-patch/79732>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [April 20, 2023, 11:43am UTC](https://community.hubspot.com/t/cannot-populate-custom-contact-properties-using-a-post-api-request-but-can-using-patch/79732 "2023-04-20T11:43:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MCrawley2](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@MCrawley2](https://community.hubspot.com/u/MCrawley2)\
**Post date:** [April 20, 2023, 11:43am UTC](https://community.hubspot.com/t/cannot-populate-custom-contact-properties-using-a-post-api-request-but-can-using-patch/79732/1 "2023-04-20T11:43:03Z")

</div>

We are testing out Hubspot and we need to store additional custom properties against the Contact entity. We have added custom properties, for example pets\_name, however we are finding that we are not able to populate this field when creating a new contact via a POST API request. It doesn’t complain when we supply the property in the request body, however the contact that is created does not contain any info in this field in the response nor the Hubspot CRM itself. We have found that we can populate this field by updating an already existing contact using a PATCH request, and we can then see the populated field when we do a subsequent GET request. What is the reason for this? I’m fairly certain we’re not doing anything wrong.

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [April 20, 2023, 8:34pm UTC](https://community.hubspot.com/t/cannot-populate-custom-contact-properties-using-a-post-api-request-but-can-using-patch/79732/2 "2023-04-20T20:34:37Z")

</div>

Hey, @MCrawley2. Thanks for your question. I have an example and a suggestion for you.

Example:

- I created a custom property called pets name (pets\_name)
- Used this endpoint **POST** `/crm/v3/objects/contacts` and used the on-page example

Request

```lia-code-sample
curl --request POST \
 --url https://api.hubapi.com/crm/v3/objects/contacts \
 --header 'authorization: Bearer YOUR_ACCESS_TOKEN' \
 --header 'content-type: application/json' \
 --data '{
 "properties": {
 "company": "Wagstaff School",
 "email": "mrfrond@bobsburgers.com",
 "firstname": "Phillip",
 "lastname": "Frond",
 "website": "bobsburgers.com",
 "pets_name": "Kitty"
 }
}'​

```

- Response

In-app view of property and the source that added it (my private app)

 ![CleanShot 2023-04-20 at 14.28.29@2x.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/d/d89298369dba042bfabe40d29bbe7167ffea9f3b.png)

My suggestion:

When posting questions, it’s helpful if you include an example request and response (for API-related questions). Not that you did anything wrong. I want to increase your chances of getting high-quality answers from the community the next time you post.

Best,

Jaycee