> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/menu/introduction.md). # Introduction This guide outlines the menu management API endpoints in the system. These endpoints allow you to generate navigation menus and breadcrumb trails dynamically based on the menu structure configured in the system. The Menu API provides functionality for: **1. Menu Generation** * Generate hierarchical navigation menus with configurable depth * Support for multi-level menu structures * Filter menus by parent node and depth height * Automatic URL generation for menu items * Category-based menu item integration * Custom attribute support for menu items **2. Breadcrumb Generation** * Generate breadcrumb trails for navigation * Support for different generator types * Automatic path traversal from root to current item * Integration with category hierarchies * Multi-language support for labels and URLs **3. Menu Structure** * Tree-based menu hierarchy using Materialized Path (MP\_Node) * Visibility control for menu items * Custom labels and URLs per menu item * Integration with category catalog system * Support for custom attributes via EAV (Entity-Attribute-Value) * Automatic parent-child relationship management Each endpoint is designed to support dynamic navigation generation for e-commerce platforms, content management systems, and web applications. **NOTE:** All methods described in this documentation use the `GET` method and do not require authentication. Menus are publicly accessible and cached for optimal performance. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://apidocs.akinon.com/commerce-openapis/menu/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.