cwdekker

<p>Sekura REST Bridge for ACF securely exposes Advanced Custom Fields in the WordPress REST API. Based on <a href="https://github.com/airesvsg/acf-to-rest-api" rel="nofollow ugc">ACF to REST API</a> by Aires Goncalves, rebuilt with security as a first-class concern.</p>
<p>The original ACF to REST API plugin exposes all ACF field data to unauthenticated requests, including options pages (which often contain API keys and secrets), user profile fields, and fields on private/draft posts. This plugin fixes that with proper WordPress capability checks on every endpoint.</p>
<h4>Features</h4>
<ul>
<li>Proper permission checks on every endpoint</li>
<li>Per-field Show in REST API / Edit in REST API toggles</li>
<li>Works alongside ACF Pro’s native REST support</li>
<li>Drop-in replacement for ACF to REST API (same acf/v3 namespace)</li>
<li>Filterable permissions for custom access control</li>
</ul>
<h4>Endpoints</h4>
<ul>
<li><code>GET /wp-json/acf/v3/{post_type}/{id}</code> – Get ACF fields for a post</li>
<li><code>GET /wp-json/acf/v3/{post_type}/{id}/{field}</code> – Get a specific field</li>
<li><code>PUT /wp-json/acf/v3/{post_type}/{id}</code> – Update ACF fields</li>
<li><code>GET /wp-json/acf/v3/options/{id}</code> – Get ACF options page fields</li>
<li><code>GET /wp-json/acf/v3/users/{id}</code> – Get ACF fields for a user</li>
<li><code>GET /wp-json/acf/v3/comments/{id}</code> – Get ACF fields for a comment</li>
</ul>
<p>ACF data is also appended as an <code>acf</code> key on standard WP REST API responses.</p>


Sekura REST Bridge for ACF

Expose Advanced Custom Fields in the WordPress REST API with proper access control.

Pericor

<p>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.<br />
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:</p>
<pre><code>{
...
  'meta': {
    'yoast_wpseo_title': "Title set from REST call"
    'yoast_wpseo_metadesc': "Meta description set from REST call"
  }
...
}
</code></pre>
<p>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!</p>
<p>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></p>
<p>Inspired as a broader alternative to <a href="https://github.com/ChazUK/wp-api-yoast-meta" rel="nofollow ugc">wp-api-yoast-meta.</a></p>
<p>Compatible with the <a href="http://v2.wp-api.org/" rel="nofollow ugc">wordpress rest api version 2.</a></p>


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.

Sekura REST Bridge for ACF vs REST API Meta Support