cwdekker

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.
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.
<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>
ACF data is also appended as an <code>acf</code> key on standard WP REST API responses.

Sekura REST Bridge for ACF

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

Fulvio Notarstefano

Austin

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.

Sekura REST Bridge for ACF vs WP API Menus