# Add API endpoint for navigation menus

**URL:** <https://community.hubspot.com/t/add-api-endpoint-for-navigation-menus/46567>\
**Category:** HubSpot Ideas\
**Tags:** api\
**Created:** [November 5, 2021, 4:50pm UTC](https://community.hubspot.com/t/add-api-endpoint-for-navigation-menus/46567 "2021-11-05T16:50:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ErikB](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/erikb/32/7115_2.png) [@ErikB](https://community.hubspot.com/u/ErikB)\
**Post date:** [November 5, 2021, 4:50pm UTC](https://community.hubspot.com/t/add-api-endpoint-for-navigation-menus/46567/1 "2021-11-05T16:50:29Z")

</div>

1. Who: Developers who hate & any company that manage a website outside of HubSpot

2. Why:

- It’s a pain to manually update your navigation menus when you have parts of your website on other platforms (e.g. an eCommerce platform outside HubSpot) where names change or product categories get added, etc.
- HubSpot Sandboxes currently do not replicate navigation menus when syncing

3. Value: Increased productivity for companies since they can just update their nav in one place and have it replicate in HubSpot.

With the push to CMS Hub, this seems like an obvious feature. The endpoint could just allow for a nested JSON payload with keys that specify the type of label of the nav item (non-link, page within HubSpot, URL link, URL link with parameters). Nested menu items could be collected underneath a “children” array key of a parent menu item.

---

<div class="post-metadata">

**Author:** ![esnna](https://avatars.discourse-cdn.com/v4/letter/e/eada6e/32.png) [@esnna](https://community.hubspot.com/u/esnna)\
**Post date:** [December 16, 2022, 3:30pm UTC](https://community.hubspot.com/t/add-api-endpoint-for-navigation-menus/46567/2 "2022-12-16T15:30:42Z")

</div>

On a client site, we have hundreds of pages. It’s a pain to know which ones are not added to the breadcrumbs menu.

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [May 2, 2023, 1:24pm UTC](https://community.hubspot.com/t/add-api-endpoint-for-navigation-menus/46567/3 "2023-05-02T13:24:08Z")

</div>

I just asked about this via a client’s enterprise level domain and the best support could do was direct me here and claim that more upvotes will help push this up in their developer’s backlog. /eyeroll

---

<div class="post-metadata">

**Author:** ![kevinfilteau](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kevinfilteau/32/72047_2.png) [@kevinfilteau](https://community.hubspot.com/u/kevinfilteau)\
**Post date:** [May 2, 2023, 1:44pm UTC](https://community.hubspot.com/t/add-api-endpoint-for-navigation-menus/46567/4 "2023-05-02T13:44:11Z")

</div>

I Upvote ! Double /eyeroll : )

---

<div class="post-metadata">

**Author:** ![DeanFrazier](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/deanfrazier/32/21810_2.png) [@DeanFrazier](https://community.hubspot.com/u/DeanFrazier)\
**Post date:** [August 31, 2026, 8:38pm UTC](https://community.hubspot.com/t/add-api-endpoint-for-navigation-menus/46567/6 "2026-08-31T20:38:00Z")

</div>

bump! 🙄🙄🙄 (triple eyeroll!)