# Properties readonly after creation

**URL:** <https://community.hubspot.com/t/properties-readonly-after-creation/135226>\
**Category:** APIs & Integrations\
**Tags:** developer-tools\
**Created:** [June 26, 2025, 9:23am UTC](https://community.hubspot.com/t/properties-readonly-after-creation/135226 "2025-06-26T09:23:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JP98](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@JP98](https://community.hubspot.com/u/JP98)\
**Post date:** [June 26, 2025, 9:23am UTC](https://community.hubspot.com/t/properties-readonly-after-creation/135226/1 "2025-06-26T09:23:22Z")

</div>

Hello team,

Some properties only allow us to set a value on creation of a new object, but not when we update it. However, there doesn’t appear to be any way for us to validate if a property can be used this way - this obviously isn’t ideal at all when allowing end users to map an integration themeselves, and they can choose any writeable property, but then their edits fail because some of the properties aren’t editable after creation. How can we manage this?

---

<div class="post-metadata">

**Author:** ![kosalaindrasiri](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kosalaindrasiri/32/44349_2.png) [@kosalaindrasiri](https://community.hubspot.com/u/kosalaindrasiri)\
**Post date:** [June 26, 2025, 7:26pm UTC](https://community.hubspot.com/t/properties-readonly-after-creation/135226/2 "2025-06-26T19:26:30Z")

</div>

Hey @JP98,

Currently, HubSpot does not expose a flag in the properties API to indicate **if a property is only writable at creation**. This creates uncertainty in integration setups where users can map to any “writable” property.

You can use _GET /crm/v3/properties/{objectType}_ to fetch the list and filter out _ **readOnlyValue: true** _ and _ **readOnlyDefinition: true** _, but keep in mind that this still won’t catch “write-once” cases.

Refer:

- [Manage view and edit access for properties](https://knowledge.hubspot.com/properties/restrict-view-edit-access-for-properties)
- [Accounts Dashboard | HubSpot](https://developers.hubspot.com/docs/guides/api/crm/properties)
- [Accounts Dashboard | HubSpot](https://developers.hubspot.com/docs/guides/api/crm/objects/custom-objects)

Regards,

---

<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:** [June 26, 2025, 8:46pm UTC](https://community.hubspot.com/t/properties-readonly-after-creation/135226/3 "2025-06-26T20:46:00Z")

</div>

Great answer, **@kosalaindrasiri 🙌** Thank you! — Jaycee

---

<div class="post-metadata">

**Author:** ![JP98](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@JP98](https://community.hubspot.com/u/JP98)\
**Post date:** [June 26, 2025, 8:57pm UTC](https://community.hubspot.com/t/properties-readonly-after-creation/135226/4 "2025-06-26T20:57:57Z")

</div>

Thanks @kosalaindrasiri - that’s what I had already been using, but it’s still super unhelpful that a property doesn’t show as readonly, yet when we push data to it, it rejects it as being read only after creation. We have no reliable way of capturing this to alert the user when they choose to push data to this property that it will only work once, and after that will break the integration.

---

<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:** [June 26, 2025, 9:09pm UTC](https://community.hubspot.com/t/properties-readonly-after-creation/135226/5 "2025-06-26T21:09:12Z")

</div>

Hey, @JP98 If you have the time, submitting your feedback for developer-related product functionality would be appreciated — [**Developer Feedback form**](https://developers.hubspot.com/feedback). Please note, it is not a support form, but it is designed for these types of comments from developers.

Best,

Jaycee