DeveloperWil

<p>Completely disables the XML-RPC API which was introduced in WordPress 3.5 and above which lets remote clients post, upload and edit content.</p>
<p>Notes:<br />
If you are using the WordPress smart phone app or the Jetpack plugin, please note that they need this service enabled.</p>
<p>If you activate this plugin your WordPress phone app will not be able to connect to your site and Jetpack will not be able to connect to wordpress.com where site visitor data (and other stuff) is stored.</p>
<p>Other plugins and services that use the XML-RPC API will also not function properly.</p>
<h4>Plugin Page</h4>
<p><a href="https://zeropointdevelopment.com/wordpress-plugins/deactivate-xml-rpc-service-wordpress-plugin/" title="Deactivate XML-RPC Service WordPress Plugin" rel="nofollow ugc">Deactivate XML-RPC</a></p>


Deactivate XML-RPC Service

Disables the XMP-RPC API service introduced in WordPress 3.5 and above.

brainvireinfo

<p>You can now disable XML-RPC to avoid Brute force attack for given IPs or can even enable access for some IPs. XML-RPC on WordPress is actually an API that gives developers who build mobile apps, desktop apps and other services, the ability to talk to a WordPress site. The XML-RPC API that WordPress provides gives developers, a way to write applications (for you) that can do many of the things that you can do when logged into WordPress via the web interface.</p>
<h4>Features</h4>
<p>Block XML-RPC by following way.</p>
<ul>
<li>Disable pingback.ping, pingback.extensions.getPingbacks and Unset X-Pingback from HTTP headers, that will block bots to access specified method.</li>
<li>Disable/Block XML-RPC for all users.</li>
</ul>


Manage XML-RPC

Enable/Disable XML-RPC for all or based on IP list, also you can control pingback and Unset X-Pingback from HTTP headers.

Deactivate XML-RPC Service vs Manage XML-RPC