Timothy Jacobs

When a network error is encountered, API clients should be able to retry a request without a risk of their request being processed twice. 
WP API Idempotence adds support for clients to include an idempotency key that uniquely identifies that request. If the server detects 
that a request with the same key has already been processed or is currently being processed, the response for the initial request will 
be returned.
For Example:
<pre><code>{
 "title": "My Important Post",
 "content": "This will only go out once!",
 "status": "draft",
 "idempotency_key": "1ced64e9-9537-4b7b-9919-444d9e15e201"
}
</code></pre>
<h4>Configuration</h4>
<ul>
<li>Idempotency key can either be passed in the request header or the request body.</li>
<li>The idempotency key name can be customized.</li>
<li>Change the HTTP methods the idempotency key is supported for. Defaults to <code>POST</code>, <code>PUT</code>, <code>PATCH</code>.</li>
</ul>
A sample request interface is included to demonstrate the selected configuration.
<h4>Developers</h4>
The plugin includes two actions to modify the dependency injection container (DIC) and insert custom services.
The <code>wp_api_idempotence_initialize_container_builder</code> action allows you to modify the Dependency Injection builder itself and 
the <code>wp_api_idempotence_initialize_container</code> action allows you to override dependencies. For example:
<pre><code>add_action( 'wp_api_idempotence_initialize_container', function( $container ) {
 $container->set( '_dataStore', DI\object( 'YourName\CustomDataStore' ) );
} );
</code></pre>
Under the hood, the plugin is made up of a <code>DataStore</code>, <code>RequestHasher</code>, <code>ResponseSerializer</code> and <code>RequestPoller</code>.
The <code>DataStore</code> is primarily responsible for retrieving or storing an idempotent request. By default, requests 
are stored in a custom database table. This could be substituted for a custom driver by implementing the <code>DataStore</code> 
interface. For example a Redis server.
The <code>RequestHasher</code> produces a unique hash for a <code>WP_REST_Request</code> object. This hash is based off of the contents of 
the request, not for the object via <code>spl_object_hash</code> or similar. This can also be substituted by implementing the 
 RequestHasher interface.
The <code>ResponseSerializer</code> converts a <code>WP_REST_Response</code> or <code>WP_Error</code> object back and forth from a string representation. 
The default JSON serializer supports filtering the serialization process using the <code>wp_api_idempotence_serialized_response_data</code> 
and <code>wp_api_idempotence_attach_serialized_response_data</code> filters. See <code>src/ResponseSerializer/Filtered.php</code>. 
The entire serializer can be substituted by implementing the <code>ResponseSerializer</code> interface.
Finally, the <code>RequestPoller</code> class polls the data store for a response if it is determined that an idempotent request 
is currently being processed when another request with the same key arrives. By default, the data store is polled 
every seconds a maximum of 15 times to try and retrieve a response object. If no response is found, an error with code 
 rest_duplicate_idempotency_key will be returned. This can be adjusted by overwriting the <code>poll.sleepSeconds</code> and 
 poll.maxQueries in the DIC. The <code>RequestPoller</code> can also be entirely subsituted by implementing the <code>RequestPoller</code> 
interface.
<h4>Contributing</h4>
This plugin is hosted on <a href="https://github.com/iron-bound-designs/wp-api-idempotence" rel="nofollow ugc">GitHub</a>. Issues and pull requests are welcomed.

WP REST API Idempotent Requests

Allow REST API clients to safely retry requests in case of network errors without risk of the request being processed twice.

Jeff Starr

Does one thing: Completely disables the WordPress REST API for visitors who are not logged into WordPress. No configuration required.
Important: This plugin completely disables the WP REST API for visitors who are NOT logged in to WordPress. So not recommended if your site needs the WP REST API for any non-logged users.
👉 The fast, simple way to prevent abuse of your site’s REST/JSON API 
👉 Protects your site’s REST data from all non-logged users and bots 
👉 Uses only 4KB of code, so super lightweight, fast, and effective
<h3>Features</h3>
<ul>
<li>Disable REST/JSON for visitors (not logged in)</li>
<li>Disables REST header in HTTP response for all users</li>
<li>Disables REST links in HTML head for all users</li>
<li>100% plug-and-play, set-it-and-forget solution</li>
</ul>
How does it work?
This plugin completely disables the WP REST API unless the user is logged into WordPress.
<ul>
<li>For logged-in users, WP REST API works normally</li>
<li>For logged-out users, WP REST API is disabled</li>
</ul>
What happens if logged-out visitor makes a JSON/REST request? They will get only a simple message:
<pre><code>rest_login_required: REST API restricted to authenticated users.
</code></pre>
This message may customized via the filter hook, <code>disable_wp_rest_api_error</code>. Check out <a href="https://wordpress.org/support/topic/not-entirely-for-non-techies/#post-12014965" rel="ugc">this post</a> for an example of how to do it.
<h3>Privacy</h3>
This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way. If anything it improves user privacy, as it protects potentially sensitive information from being displayed/accessed via REST API.
Disable WP REST API is developed and maintained by <a href="https://x.com/perishable" rel="nofollow ugc">Jeff Starr</a>, 15-year <a href="https://plugin-planet.com/" rel="nofollow ugc">WordPress developer</a> and <a href="https://books.perishablepress.com/" rel="nofollow ugc">book author</a>.
<h3>Support development of this plugin</h3>
I develop and maintain this free plugin with love for the WordPress community. To show support, you can <a href="https://monzillamedia.com/donate.html" rel="nofollow ugc">make a donation</a> or purchase one of my books:
<ul>
<li><a href="https://wp-tao.com/" rel="nofollow ugc">The Tao of WordPress</a></li>
<li><a href="https://digwp.com/" rel="nofollow ugc">Digging into WordPress</a></li>
<li><a href="https://htaccessbook.com/" rel="nofollow ugc">.htaccess made easy</a></li>
<li><a href="https://wp-tao.com/wordpress-themes-book/" rel="nofollow ugc">WordPress Themes In Depth</a></li>
<li><a href="https://books.perishablepress.com/downloads/wizards-collection-sql-recipes-wordpress/" rel="nofollow ugc">Wizard’s SQL Recipes for WordPress</a></li>
</ul>
And/or purchase one of my premium WordPress plugins:
<ul>
<li><a href="https://plugin-planet.com/bbq-pro/" rel="nofollow ugc">BBQ Pro</a> – Blazing fast WordPress firewall</li>
<li><a href="https://plugin-planet.com/blackhole-pro/" rel="nofollow ugc">Blackhole Pro</a> – Automatically block bad bots</li>
<li><a href="https://plugin-planet.com/banhammer-pro/" rel="nofollow ugc">Banhammer Pro</a> – Monitor traffic and ban the bad guys</li>
<li><a href="https://plugin-planet.com/ga-google-analytics-pro/" rel="nofollow ugc">GA Google Analytics Pro</a> – Connect WordPress to Google Analytics</li>
<li><a href="https://plugin-planet.com/head-meta-pro/" rel="nofollow ugc">Head Meta Pro</a> – Ultimate Meta Tags for WordPress</li>
<li><a href="https://plugin-planet.com/simple-ajax-chat-pro/" rel="nofollow ugc">Simple Ajax Chat Pro</a> – Unlimited chat rooms</li>
<li><a href="https://plugin-planet.com/usp-pro/" rel="nofollow ugc">USP Pro</a> – Unlimited front-end forms</li>
</ul>
Links, tweets and likes also appreciated. Thank you! 🙂

Disable WP REST API

while the plugin si deadsimple and very low resource impact, keep in mind that there are plugins that need the rest to work with no auth (ex. contact form 7).

dead simple and efficient, but be aware

Disables the WP REST API for visitors not logged into WordPress.

WP REST API Idempotent Requests vs Disable WP REST API