<?xml version="1.0" encoding="UTF-8" standalone="yes"?><oembed><version><![CDATA[1.0]]></version><provider_name><![CDATA[Developer Resources]]></provider_name><provider_url><![CDATA[https://developer.wordpress.com]]></provider_url><author_name><![CDATA[Justin Shreve]]></author_name><author_url><![CDATA[https://developer.wordpress.com/author/justin/]]></author_url><title><![CDATA[REST API Resources]]></title><type><![CDATA[link]]></type><html><![CDATA[<p>Welcome to the WordPress.com REST API. Below, you&#8217;ll find a full listing of all the available endpoints. As we add more endpoints, they will be automatically documented here and available through the <a href="https://developer.wordpress.com/docs/api/console/">Developer Console</a>.</p>
<p>If you&#8217;re not sure how to make calls to the API, you might want to check out the <a href="https://developer.wordpress.com/docs/api/getting-started/">Getting Started</a> guide or the walkthrough on <a href="https://developer.wordpress.com/docs/oauth2/">authentication</a>.</p>
<p>For more information about a particular endpoint, click on its name under the Resource header. You&#8217;ll be taken to the endpoint&#8217;s documentation page, which includes what query parameters the endpoint will accept, what the JSON object&#8217;s parameters will be in the response, and an example query/response.</p>
<p>This documentation is for our most recent version of the REST API, version 1.1. Documentation is still available for <a href="https://developer.wordpress.com/docs/api/v1/">version 1</a> of the REST API.</p>
<p>If you&#8217;re looking for the WordPress REST API that shipped as part of WordPress core in version 4.7, see <a href="https://developer.wordpress.org/rest-api/">its documentation</a>.  Note that this API is also enabled on WordPress.com, but the URL structure on WordPress.com is slightly different than for self-hosted sites.  See <a href="https://developer.wordpress.com/2016/11/11/wordpress-rest-api-on-wordpress-com/">this post</a> for more details.</p>
<hr />
]]></html></oembed>