Andrew MAGIK

<p>This plugin will add separate WordPress REST API (v2) endpoint, with all relations between existing post types and attached to them terms (taxonomies).<br />
It is very useful when you need to create some filters, when you want to know what taxonomies are attached to the current post type.</p>
<p>For example what can you get, using <code>wp-json/wp/v2/post-type-taxonomies</code> request (empty results not included):</p>
<pre><code>{
    post: [
        "category",
        "post_tag",
        "post_format"
    ],
    portfolio: [
        "technologies",
        "clients",
        "work_types"
    ]
}
</code></pre>
<p>Check my other useful rest-api plugins: <a href="https://wordpress.org/plugins/tags/andrew-magik-rest-api" rel="ugc">https://wordpress.org/plugins/tags/andrew-magik-rest-api</a>.</p>


WP REST API – Post Type Taxonomies

Very useful to know all attached taxonomies for post types. With this information you can create separate filters for specified post types.



Very useful to know all attached taxonomies for post types

This plugin show all relations between existing post types and attached to them terms (taxonomies) in separate WordPress REST API (v2) endpoint.

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.

WP REST API – Post Type Taxonomies vs Sekura REST Bridge for ACF