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.

Josh Pollock

Provides useful tools for optimizing a WordPress site to power a single page web app using WordPress REST API. Designed to work as a companion for the <a href="https://github.com/shelob9/josie" rel="nofollow ugc">Josie REST API-powered starter app</a> but useful for any site using the WordPress REST API.
This is a companion plugin for my WordPress REST API (WP-API) powered application starter, called <a href="https://github.com/shelob9/josie" rel="nofollow ugc">Josie</a>. It can be used with any site running the <a href="http://wp-api.org/" rel="nofollow ugc">WordPress REST API</a>.
It packages multiple libraries, most of which I wrote, to accomplish several things:
1) <a href="https://github.com/shelob9/jp-rest-cache" rel="nofollow ugc">Provides a soft-expiring, server-side cache for requests to the REST API</a>.
2) <a href="https://github.com/Shelob9/jp-tax-query" rel="nofollow ugc">Adds routes and endpoints for making tax-queries</a>.
3) <a href="https://github.com/Shelob9/jp-menu-route" rel="nofollow ugc">Adds routes and endpoints for getting menus & menu items</a>.
4) <a href="https://github.com/Shelob9/jp-rest-access" rel="nofollow ugc">Adds cross-domain headers, and for the posts endpoint allows for page offsets and limits the number of posts_per_page</a>.

Josie API

Adds endpoints for menus & tax-queries, as well as a server-side cache and CORS headers for the WordPress REST API.

Sekura REST Bridge for ACF vs Josie API