# Error accessing custom contact properties through API

**URL:** <https://community.hubspot.com/t/error-accessing-custom-contact-properties-through-api/136511>\
**Category:** APIs & Integrations\
**Tags:** developer-tools\
**Created:** [July 18, 2025, 9:20pm UTC](https://community.hubspot.com/t/error-accessing-custom-contact-properties-through-api/136511 "2025-07-18T21:20:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![seanrichter](https://avatars.discourse-cdn.com/v4/letter/s/919ad9/32.png) [@seanrichter](https://community.hubspot.com/u/seanrichter)\
**Post date:** [July 18, 2025, 9:20pm UTC](https://community.hubspot.com/t/error-accessing-custom-contact-properties-through-api/136511/1 "2025-07-18T21:20:41Z")

</div>

I have several custom contact preoprties that I cannot read through teh API using the hubspot client. I make the call and receive an erorr like the property doesn’t exist. I double checked the property label, name, and internal name. They are the same.

“Unable to infer object type from: clients\_invited”

---

<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:** [July 18, 2025, 9:28pm UTC](https://community.hubspot.com/t/error-accessing-custom-contact-properties-through-api/136511/2 "2025-07-18T21:28:13Z")

</div>

Hey, @seanrichter 👋 Can you share a simple example? Seeing how your request URL and body and the response JSON are formatted is helpful to our community members. I like to use Postman for this kind of test as it helps keep things simple and easy to copy and paste back here. — Jaycee

---

<div class="post-metadata">

**Author:** ![seanrichter](https://avatars.discourse-cdn.com/v4/letter/s/919ad9/32.png) [@seanrichter](https://community.hubspot.com/u/seanrichter)\
**Post date:** [July 18, 2025, 9:38pm UTC](https://community.hubspot.com/t/error-accessing-custom-contact-properties-through-api/136511/3 "2025-07-18T21:38:30Z")

</div>

const contact = await hubspotClient.crm.contacts.basicApi.getById(  
id,  
undefined,  
undefined,  
[  
‘clients\_invited’,  
],  
true  
);

---

<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:** [July 22, 2025, 6:02pm UTC](https://community.hubspot.com/t/error-accessing-custom-contact-properties-through-api/136511/4 "2025-07-22T18:02:54Z")

</div>

Hey, @seanrichter 👋 In this case, I think we need a bit if a different example from you. Can you jump over to Postman and set up a basic example of your request? And add the full URL and JSON body (if used). I ask because the error you shared in your original example shows an `object` type error and not a `property` type error. This makes me think the request URL isn’t set up correctly. — Jaycee

---

<div class="post-metadata">

**Author:** ![seanrichter](https://avatars.discourse-cdn.com/v4/letter/s/919ad9/32.png) [@seanrichter](https://community.hubspot.com/u/seanrichter)\
**Post date:** [July 22, 2025, 6:44pm UTC](https://community.hubspot.com/t/error-accessing-custom-contact-properties-through-api/136511/5 "2025-07-22T18:44:30Z")

</div>

The update is I found that custom contact properties do not store version history. The API call through the client was accurate.