# Create Contact Response Datetime

**URL:** <https://community.hubspot.com/t/create-contact-response-datetime/19882>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [April 6, 2020, 4:12pm UTC](https://community.hubspot.com/t/create-contact-response-datetime/19882 "2020-04-06T16:12:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MGO](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mgo/32/59606_2.png) [@MGO](https://community.hubspot.com/u/MGO)\
**Post date:** [April 6, 2020, 4:12pm UTC](https://community.hubspot.com/t/create-contact-response-datetime/19882/1 "2020-04-06T16:12:38Z")

</div>

Hi together, when I create a contact with the new v3 Contact Endpoint, the response object contains wrong values for createdAt and updatedAt. As the values are

“1970-01-01T00:00:00Z”, I asume they are actually Null.  
If I look up the created contact with the get contact endpoint I receive the right values.  
The same scenario works in the company api totally fine.

Here is my request and the response:  
[https://api.hubapi.com/crm/v3/objects/contacts?hapikey={{hubspotApiKey}](https://api.hubapi.com/crm/v3/objects/contacts?hapikey=%7B%7BhubspotApiKey%7D)}

 ![createContactResponse.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/1/9/1976e820c4c173d8c5c2fc18a1759db629eb77b7.png)

Someone else having the same issue?  
Thanks for any answer!

---

<div class="post-metadata">

**Author:** ![WendyGoh](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wendygoh/32/42320_2.png) [@WendyGoh](https://community.hubspot.com/u/WendyGoh)\
**Post date:** [April 8, 2020, 3:37am UTC](https://community.hubspot.com/t/create-contact-response-datetime/19882/2 "2020-04-08T03:37:34Z")

</div>

Hey @MGO,

Thanks for pointing this out! On my end, I’m able to observe a similar behavior as well.

It seems that the created date property is populating the correct date time and I’m able to see the correct `createdAt` and `updatedAt` value when I GET crm/v3/objects/contacts/{contactId}. However, the POST crm/v3/objects/contacts return response is showing `1970-01-01T00:00:00Z`.

In this case, I’ll have to reach out to our internal team and I’ll keep you posted here!

---

<div class="post-metadata">

**Author:** ![MGO](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mgo/32/59606_2.png) [@MGO](https://community.hubspot.com/u/MGO)\
**Post date:** [April 16, 2020, 8:00am UTC](https://community.hubspot.com/t/create-contact-response-datetime/19882/3 "2020-04-16T08:00:37Z")

</div>

Hey @WendyGoh,

any resolutions on this issue?

---

<div class="post-metadata">

**Author:** ![WendyGoh](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wendygoh/32/42320_2.png) [@WendyGoh](https://community.hubspot.com/u/WendyGoh)\
**Post date:** [April 17, 2020, 2:47am UTC](https://community.hubspot.com/t/create-contact-response-datetime/19882/4 "2020-04-17T02:47:19Z")

</div>

Hey @MGO,

Our team is still looking into this and I’ll keep you posted as soon as I hear back from them.

---

<div class="post-metadata">

**Author:** ![WendyGoh](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wendygoh/32/42320_2.png) [@WendyGoh](https://community.hubspot.com/u/WendyGoh)\
**Post date:** [April 20, 2020, 10:41am UTC](https://community.hubspot.com/t/create-contact-response-datetime/19882/5 "2020-04-20T10:41:45Z")

</div>

Hey @MGO,

Here’s an update! Our team has pushed a fix for this issue. On my end, upon creating a contact via the crm/v3/objects/contacts endpoint, I’m not seeing the following value:

`1970-01-01T00:00:00Z`

for both the `createdAt` and `updatedAt` key.

Could you try and see if all’s well on your end?

---

<div class="post-metadata">

**Author:** ![MGO](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mgo/32/59606_2.png) [@MGO](https://community.hubspot.com/u/MGO)\
**Post date:** [April 20, 2020, 11:07am UTC](https://community.hubspot.com/t/create-contact-response-datetime/19882/6 "2020-04-20T11:07:50Z")

</div>

Hey @WendyGoh,

yes the bug is fixed.

Thanks!