Daniel Bachhuber

Ryan McCue

Jonny Harris

Joe Hoyle

Rachel Baker

This plugin uses the OAuth 1.0a protocol to allow delegated authorization; that is, to allow applications to access a site using a set of secondary credentials. This allows server administrators to control which applications can access the site, as well as allowing users to control which applications have access to their data.
This plugin only supports WordPress >= 4.4.
The latest stable version is also available from the <a href="https://wordpress.org/plugins/rest-api-oauth1/" rel="ugc">WordPress Plugin Directory</a>.
<h3>New to OAuth</h3>
We strongly recommend you use an existing OAuth library. You’ll be best off if you understand the authorization process, but leave the actual implementation to well-tested libraries, as there are a lot of edge cases.
Start reading from <a href="docs/introduction/README.md" rel="nofollow ugc">the Introduction</a> to get started!
<h3>For OAuth Veterans</h3>
If you already know how to use OAuth, here’s the lowdown:
<ul>
<li>The plugin uses OAuth 1.0a in</li>
<li>We use the three-legged flow</li>
<li>To find the REST API index, apply the <a href="http://v2.wp-api.org/guide/discovery/" rel="nofollow ugc">API autodiscovery process</a></li>
<li>The endpoints for the OAuth process are available in the REST API index: check for <code>$.authentication.oauth1</code> in the index data.
<ul>
<li>The temporary credentials (request token) endpoint is <code>$.authentication.oauth1.request</code> (typically <code>/oauth1/request</code>)</li>
<li>The authorization endpoint is <code>$.authentication.oauth1.authorize</code> (typically <code>/oauth1/authorize</code>)</li>
<li>The token exchange (access token) endpoint is <code>$.authentication.oauth1.access</code> (typically <code>/oauth1/access</code>)</li>
</ul>
</li>
<li>Your callback URL must match the registered callback URL for the application in the scheme, authority (user/password) host, port, and path sections. (Subpaths are not allowed.)</li>
<li>The only signature method supported is HMAC-SHA1.</li>
<li>OAuth parameters are supported in the Authorization header, query (GET) parameters, or request body (POST) parameters (if encoded as <code>application/x-www-form-urlencoded</code>). OAuth parameters are not supported in JSON data.</li>
</ul>

WP REST API – OAuth 1.0a Server

Hello, I have made an adapter for Parse Server under Node.js with which you can link the login of any installation of wordpress in Parse Server, for that I have used your plugin, which is the one that gives us access_token and allows us to verify the authenticity Of the user registered in the server.

https://github.com/enriquecerda/parse-server-wordpress-login

Links with Parse-server Node.js

Got this working after some good amount of work! Thanks for bringing this and making API calls secure.

Worked like a charm!

Really Useful And Good Plugin
But Please
1- Reply on The Support Forum
2- Update it To Work Good With Last WordPress Verison
3 – No Clear Docs
4 - not work with localhost

Good But

Connect applications to your WordPress site without ever giving away your password.

Samuel Aguilera

The WordPress REST API is a great resource, but if you don’t want to use it probably you will want to close this door to your WordPress.
Unlike other popular plugins that aims to disable the REST API but only return an error, processed by the REST API, when a request is received, by default, this plugin removes all filters and actions related to WordPress REST API, and returns a 404 error for requests sent to the REST API URL endpoints, effectively blocking any use of the REST API.
Optionally you can set the REST API setting in Settings -> General page to “Logged In Only” for a less drastical action, to keep REST API access enabled but require the user to be logged in to accept the requests.
If you’re happy with the plugin <a href="https://wordpress.org/plugins/sar-disable-rest-api/reviews/?filter=5" rel="ugc">please don’t forget to give it a good rating</a>, it will motivate me to keep sharing and improving this plugin (and others).
SUPPORT: If you have any support question, please <a href="https://github.com/samuelaguilera/sar-disable-rest-api/issues" rel="nofollow ugc">create an issue at the Github repository</a>.
<h4>Requirements</h4>
<ul>
<li>WordPress 4.7 or higher.</li>
</ul>
<h4>Features</h4>
<ul>
<li>Disable WordPress core REST API for real by removing all filters and actions related to it and returning a 404 error for requests sent to REST API URL endpoints (e.g. https://example.com/wp-json/whatever ).</li>
<li>Option to require user to be logged in to use the REST API instead of completely disable it.</li>
</ul>
<h4>Usage</h4>
To disable the REST API completely simply install the plugin from the Plugins page and enable it.
If you don’t want to disable the REST API but require user to be logged in instead, go to Settings -> General page and set the REST API to option to “Logged In Only”, and click Save Changes.
You can change the option back to “Off” if you want to disable the REST API again.
To return to WordPress default, simply deactivate the plugin.

Disable REST API for Real

A simple way to disable WordPress REST API.



One click plugin

Really prevents the REST API from handling requests (default) or require user to be logged in.

WP REST API – OAuth 1.0a Server vs Disable REST API for Real