Gunjan Jaswal

EndPointy Menus adds custom REST API routes to expose your WordPress navigation menus as JSON.
Base namespace: <code>endpointy-menus/v1</code>
Endpoints:
<ul>
<li>
<code>GET /wp-json/endpointy-menus/v1/menus</code> 
Returns all registered menus with locations and items.
</li>
<li>
<code>GET /wp-json/endpointy-menus/v1/menus/<id></code> 
Returns a single menu and its items by menu ID.
</li>
<li>
<code>GET /wp-json/endpointy-menus/v1/locations</code> 
Returns all registered menu locations with assigned menus.
</li>
<li>
<code>GET /wp-json/endpointy-menus/v1/locations/<location></code> 
Returns a menu assigned to a specific location (e.g., ‘primary’, ‘footer’).
</li>
</ul>
Query Parameters:
<ul>
<li><code>nested=true</code> – Returns menu items in a hierarchical tree structure with parent-child relationships. 
Example: <code>/wp-json/endpointy-menus/v1/menus/2?nested=true</code></li>
</ul>
This is useful for headless WordPress setups or any external app that needs to read your menu structure.
<h3>Usage</h3>
Example requests:
Get all menus: 
 https://your-site.com/wp-json/endpointy-menus/v1/menus
Get single menu by ID: 
 https://your-site.com/wp-json/endpointy-menus/v1/menus/2
Get all menu locations: 
 https://your-site.com/wp-json/endpointy-menus/v1/locations
Get menu by location (e.g., ‘primary’): 
 https://your-site.com/wp-json/endpointy-menus/v1/locations/primary
Get nested menu structure: 
 https://your-site.com/wp-json/endpointy-menus/v1/menus/2?nested=true 
 https://your-site.com/wp-json/endpointy-menus/v1/locations/primary?nested=true
Use these URLs directly from your front-end application or API client.
<h3>Support the Developer</h3>
If you find this plugin useful, you can support the developer:
<ul>
<li>Website: https://gunjanjaswal.me</li>
<li>GitHub: https://github.com/gunjanjaswal/Endpointy-Menus</li>
<li>Ko-fi: https://ko-fi.com/gunjanjaswal</li>
</ul>
<h3>Contributing</h3>
Contributions, issues, and feature requests are welcome! 
GitHub: https://github.com/gunjanjaswal/Endpointy-Menus 
Issues: https://github.com/gunjanjaswal/Endpointy-Menus/issues

EndPointy Menus

Expose WordPress menus via a custom REST API endpoint for headless and external applications.

Joe Bailey-Roberts

Logged in users are redirected to the editor screen for the post, while non-logged in users must log in first. This means that you can share a readable link straight to the editor, depending on your permalink settings.
Good for task management or organisation resource management.
<h3>What the plugin actually does</h3>
In simple terms, the plugin removes the frontend of the WordPress site. Post permalinks go straight to the editor page, and the theme is mostly redundant.
<h3>Why would I want to do that?</h3>
This is definitely not a useful plugin for a public-facing website. Instead, this allows you to convert WordPress into a headless CMS for managing tasks, content and more, all protected by the standard user role system. You can share a post permalink with a collaborator and they will be directed straight to the editor screen.
Maybe you want to go a step further and create an external application to display your WordPress content elsewhere using the API. In this case you definitely don’t want the standard WP frontend accessible!

WP Headless

A lightweight plugin to disable the WP frontend experience.

EndPointy Menus vs WP Headless