# HubSpotCRM custom object objectType

**URL:** <https://community.hubspot.com/t/hubspotcrm-custom-object-objecttype/140730>\
**Category:** APIs & Integrations\
**Tags:** developer-tools\
**Created:** [October 8, 2025, 8:40am UTC](https://community.hubspot.com/t/hubspotcrm-custom-object-objecttype/140730 "2025-10-08T08:40:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Prateek\_Boomi](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Prateek\_Boomi](https://community.hubspot.com/u/Prateek_Boomi)\
**Post date:** [October 8, 2025, 8:40am UTC](https://community.hubspot.com/t/hubspotcrm-custom-object-objecttype/140730/1 "2025-10-08T08:40:48Z")

</div>

Our team is working on a HubSpotCRM connector, adding support for custom objects. To perform basic API operations for custom objects, we need a consistent objectType value for the API endpoint URLs (eg. [https://api.hubapi.com/crm/v3/objects/{objectType}/{objectId](https://api.hubapi.com/crm/v3/objects/%7BobjectType%7D/%7BobjectId)}) that won’t change as we move between different environments (e.g. staging, production, etc.).

We’ve explored several options and believe that using a prefix like “ **p\_** ” on the custom object’s name will generate a stable objectType that remains consistent across all our environments.

We’d greatly appreciate any confirmation or insights from the community on whether this is a reliable and recommended approach. Are there any potential issues or alternative best practices we should be aware of?

---

<div class="post-metadata">

**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\
**Post date:** [October 8, 2025, 10:37am UTC](https://community.hubspot.com/t/hubspotcrm-custom-object-objecttype/140730/2 "2025-10-08T10:37:40Z")

</div>

Hi [@Prateek\_Boomi](https://community.hubspot.com/t5/user/viewprofilepage/user-id/999432) and thank you for bringing such a thoughtful question to the HubSpot Community! 🧡

Firstly, it’s awesome that your team is working on a HubSpot CRM connector with custom object support, this kind of extensibility is what makes the platform so powerful.  
For reference, here is the documentation about it “[Custom objects API guide](https://developers.hubspot.com/docs/api-reference/crm-custom-objects-v3/guide)”.  
Now, let’s consult with our Top Experts: Hi [@sylvain\_tirreau](https://community.hubspot.com/t5/user/viewprofilepage/user-id/601366), @Anton and @MichaelMa do you have suggestions to help [@Prateek\_Boomi](https://community.hubspot.com/t5/user/viewprofilepage/user-id/999432), please?  
Have a great day and thanks so much!  
Bérangère

---

<div class="post-metadata">

**Author:** ![MichaelMa](https://avatars.discourse-cdn.com/v4/letter/m/b5ac83/32.png) [@MichaelMa](https://community.hubspot.com/u/MichaelMa)\
**Post date:** [October 8, 2025, 12:19pm UTC](https://community.hubspot.com/t/hubspotcrm-custom-object-objecttype/140730/3 "2025-10-08T12:19:54Z")

</div>

As long as the object’s internal name/slug is the same in all the systems then yes, you can access the custom object with p\_{internal\_name}. Eg, p\_account\_teams. The labels can be chcanged but the internal name is locked once the object is created.

 ![MichaelMa_0-1759925835571.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/2/9/294211cd2832c261883e45c76f3b50e9b841d8fa.png)

If nothing else, you can use the same notation to pull the schema to get the object id which you can also use.

Since API v3, I’ve used the p\_{internal\_name} format for all my API calls and haven’t had any issues with it.