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.

Chris Hutchinson

ramvi

kokarn

Puts all ACF fields from posts, pages, custom post types, comments, attachments and taxonomy terms, into the WP-API output under the ‘acf’ key. Creates a new <code>/option</code> endpoint returning options (requires ACF Options Page plugin).

ACF to WP-API

Works like it says it will.  Good documentation.



Does what it says on the tin

Plugs Advanced Custom Fields (ACF) data into the WordPress JSON API (WP-API).

REST API Meta Support vs ACF to WP-API