Alvind

Enabling the ability to set your own WordPress REST API Prefix (/wp-json).
<h4>Contribute to Custom REST API Prefix</h4>
Development for this plugin happens in a public GitHub repository. If you have a suggestion, bug report, patch, or pull request, please feel free to <a href="https://github.com/alvindcaesar/custom-rest-api-prefix" rel="nofollow ugc">contribute here</a>.

Custom REST API Prefix

A simple plugin to customize the default WordPress REST API prefix.

Austin

Fulvio Notarstefano

This plugin extends the <a href="https://wordpress.org/plugins/json-rest-api/" rel="ugc">WordPress JSON REST API</a> with new routes for WordPress registered menus
The new routes available will be:
<ul>
<li><code>/menus</code> list of every registered menu.</li>
<li><code>/menus/<id></code> data for a specific menu.</li>
<li><code>/menu-locations</code> list of all registered theme locations.</li>
<li><code>/menu-locations/<location></code> data for menu in specified menu in theme location.</li>
</ul>
Currently, the <code>menu-locations/<location></code> route for individual menus will return a tree with full menu hierarchy, with correct menu item order and listing children for each menu item. The <code>menus/<id></code> route will output menu details and a flat array of menu items. Item order or if each item has a parent will be indicated in each item attributes, but this route won’t output items as a tree.
You can alter the data arrangement of each individual menu items and children using the filter hook <code>json_menus_format_menu_item</code>.
An important note on WP API V2:
In V1 the routes are located by default at <code>wp-json/menus/</code> etc.
In V2 the routes by default are at <code>wp-json/wp-api-menus/v2/</code> (e.g. <code>wp-json/wp-api-menus/v2/menus/</code>, etc.) since V2 encourages prefixing and version namespacing.

WP API Menus

It Does!

Extends WordPress WP REST API with new routes pointing to WordPress menus.

Custom REST API Prefix vs WP API Menus