Pericor

Automatically stores the meta data from the <code>meta</code> field of a wordpress REST API posts (<a href="https://developer.wordpress.org/rest-api/reference/posts/#create-a-post" rel="nofollow ugc">/wp-json/wp/v2/posts</a>) or pages (<a href="https://developer.wordpress.org/rest-api/reference/pages/#create-a-page" rel="nofollow ugc">/wp-json/wp/v2/pages</a>) POST in the meta data associated with the created page or post using <a href="https://developer.wordpress.org/reference/functions/update_post_meta/" rel="nofollow ugc">update_post_meta</a>. The key / value information sent in the REST POST ‘meta’ object field is stored as both ‘key’ and ‘_key’ to support different plugin formats. 
For example, if trying to set the YOAST SEO Plugin values dynamically when creating a page from the REST API, you would simply add the fields to the meta field of the REST POST data when you POST the endpoint, and the plugin values will be added to the page:
<pre><code>{
...
 'meta': {
 'yoast_wpseo_title': "Title set from REST call"
 'yoast_wpseo_metadesc': "Meta description set from REST call"
 }
...
}
</code></pre>
Use this plugin when dynamically creating pages with the WordPress REST API to support modifying plugin settings for pages/posts created using the REST API!
A guide on how to use this plugin to generate a page/post with plugins configured from the REST API is <a href="https://www.pericror.com/software/generating-pages-posts-plugins-using-wordpress-rest-api/" rel="nofollow ugc">available at Pericror.</a>
Inspired as a broader alternative to <a href="https://github.com/ChazUK/wp-api-yoast-meta" rel="nofollow ugc">wp-api-yoast-meta.</a>
Compatible with the <a href="http://v2.wp-api.org/" rel="nofollow ugc">wordpress rest api version 2.</a>

REST API Meta Support

This plugin was developed and used to generate pages with a review plugin configured programatically using the rest API per page and works as described.

Works as Described

Stores meta data (i.e plugin settings) from the meta field of a WP REST API posts or pages POST creation call in the created page or post meta data.

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.

REST API Meta Support vs WP API Menus