Frankie Jarrett

Did you find this plugin helpful? Please consider <a href="https://wordpress.org/support/view/plugin-reviews/json-rest-api-force-ssl" rel="ugc">leaving a 5-star review</a>.
Note: This plugin requires the <a href="https://wordpress.org/plugins/json-rest-api/" rel="ugc">WP REST API (WP API)</a> plugin.
For site owners who want the WP REST API served over SSL always and forever.
All HTTP requests to the WP REST API will be 301 redirected to their HTTPS equivalent.
Also, don’t use this plugin unless you have an SSL certificate as your endpoints will break! 🙂
Development of this plugin is done <a href="https://github.com/fjarrett/json-rest-api-force-ssl" rel="nofollow ugc">on GitHub</a>. Pull requests welcome. Please see <a href="https://github.com/fjarrett/json-rest-api-force-ssl/issues" rel="nofollow ugc">issues reported</a> there before going to the plugin forum.

WP REST API Force SSL

Force WP REST API endpoints to only be served over HTTPS.

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).

WP REST API Force SSL vs ACF to WP-API