Ready to get started?Download WordPress

Plugin Directory

Secure XML-RPC

More secure wrapper for the WordPress XML-RPC interface.

How do I use the new authorization?

The old username/password paradigm can still be used, but will result in a X-Deprecated header being returned by the server.

From now on, you will send an Authorization header. This header will be the publishing application's public key, two pipe (|) characters, and a base64-encoded sha256 hash of the application's secret key concatenated with the body of the request.


Say your application has the following information: * Public Key: b730db0864b0d4453ba6a26ad6613cd4 * Secret Key: 7647a19f5bf3e9fd001419900ad48a54

And you want to make the following request (whitespace/indentation added for readability):

<?xml version="1.0"?>

Note that the second and third parameters (traditionally username and password) are empty. Usernames and passwords can still be specified, but will result in the server returning an X-Deprecated header.

Your Authorization header would thus become:


The second part of the header is generated by calculating:

base64( sha256( '7647a19f5bf3e9fd001419900ad48a54' + {request_body} ) )

WordPress will read the header and log you in as usual, but you never need to send your password across the wire.

In this paradigm, application secret keys should also be treated as passwords - they are sensitive information!

Requires: 3.8 or higher
Compatible up to: 3.8.3
Last Updated: 2014-1-1
Downloads: 505


5 stars
5 out of 5 stars


Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.