# Ability to setup Conditional Options using the API

**URL:** <https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559>\
**Category:** HubSpot Ideas\
**Tags:** api\
**Created:** [June 18, 2024, 8:59am UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559 "2024-06-18T08:59:00Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![CCristev](https://avatars.discourse-cdn.com/v4/letter/c/82dd89/32.png) [@CCristev](https://community.hubspot.com/u/CCristev)\
**Post date:** [June 18, 2024, 8:59am UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/1 "2024-06-18T08:59:00Z")

</div>

Hi,

With the recent addition of Conditional Options ([Limit available options based on a controlling property](https://knowledge.hubspot.com/properties/set-up-conditional-options-for-properties)), we are now able to set up conditional options through the HubSpot interface.

However, at the moment, there’s no easy way to set up conditional options through the API. And the process can be tedious for uses cases such as the Country \<\> State relationship, where a given country may have dozens of states to set up manually.

**Therefore, could you please look into adding a new endpoint to the API?**

---

<div class="post-metadata">

**Author:** ![JanoschFranke](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@JanoschFranke](https://community.hubspot.com/u/JanoschFranke)\
**Post date:** [October 10, 2024, 11:36am UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/2 "2024-10-10T11:36:31Z")

</div>

Good Idea, I was looking for the same.

---

<div class="post-metadata">

**Author:** ![StanBartczak](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stanbartczak/32/10239_2.png) [@StanBartczak](https://community.hubspot.com/u/StanBartczak)\
**Post date:** [November 29, 2024, 3:54pm UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/3 "2024-11-29T15:54:42Z")

</div>

This is needed by our clients

---

<div class="post-metadata">

**Author:** ![OBojahr](https://avatars.discourse-cdn.com/v4/letter/o/7c8e57/32.png) [@OBojahr](https://community.hubspot.com/u/OBojahr)\
**Post date:** [December 11, 2024, 9:56am UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/4 "2024-12-11T09:56:50Z")

</div>

If you consider this, maybe also an option to make it accessible via workflows as well.

---

<div class="post-metadata">

**Author:** ![AmberGillie](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@AmberGillie](https://community.hubspot.com/u/AmberGillie)\
**Post date:** [February 5, 2025, 11:37am UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/5 "2025-02-05T11:37:13Z")

</div>

This is a much needed resource and it’s not a heavy request. I have just switched over to hubspot after working with Zoho for many years and I am realizing how good I had it on the zoho side. Not so say hubspot doesn’t have its advantages but the API development needs to be made a priority.

---

<div class="post-metadata">

**Author:** ![fosch](https://avatars.discourse-cdn.com/v4/letter/f/ba8739/32.png) [@fosch](https://community.hubspot.com/u/fosch)\
**Post date:** [February 14, 2025, 8:18am UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/6 "2025-02-14T08:18:04Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![FelipeV](https://avatars.discourse-cdn.com/v4/letter/f/c37758/32.png) [@FelipeV](https://community.hubspot.com/u/FelipeV)\
**Post date:** [October 29, 2025, 11:14am UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/7 "2025-10-29T11:14:37Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![EdoardoP](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@EdoardoP](https://community.hubspot.com/u/EdoardoP)\
**Post date:** [November 19, 2025, 4:40pm UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/8 "2025-11-19T16:40:59Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![pharcyde](https://avatars.discourse-cdn.com/v4/letter/p/b2d939/32.png) [@pharcyde](https://community.hubspot.com/u/pharcyde)\
**Post date:** [July 17, 2026, 12:45pm UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/9 "2026-07-17T12:45:19Z")

</div>

Still needed in 2026

---

<div class="post-metadata">

**Author:** ![Bob2245](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bob2245/32/73707_2.png) [@Bob2245](https://community.hubspot.com/u/Bob2245)\
**Post date:** [October 27, 2026, 2:02pm UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/11 "2026-10-27T14:02:53Z")

</div>

Set up **and**  **read** as well! Probably the more powerful usecase of the two is being able to read the HubSpot internal logic so you can enforce it in external systems and integrations without having to manually update integration logic every time something changes in HubSpot.

---

<div class="post-metadata">

**Author:** ![DHicks9](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@DHicks9](https://community.hubspot.com/u/DHicks9)\
**Post date:** [October 27, 2026, 2:47pm UTC](https://community.hubspot.com/t/ability-to-setup-conditional-options-using-the-api/109559/12 "2026-10-27T14:47:24Z")

</div>

100% this would be extremely useful for us as well. It helps us audit downstream effects of changes we make, etc.
