meetcpatel907

<p>GrowthSEO – Content Sync adds a secure REST API endpoint to your WordPress site so GrowthSEO can publish or update posts remotely. It uses an API key you control in WordPress settings, and supports featured images and HTML/Markdown content.</p>
<ul>
<li>Improved Authorization</li>
<li>Endpoints: <code>GET /wp-json/growthseo/v1/ping</code>, <code>POST /wp-json/growthseo/v1/publish</code></li>
<li>Accepts <code>title</code>, <code>slug</code>, <code>content_html</code> or <code>content_markdown</code>, optional <code>metaDescription</code>, <code>heroImageUrl</code>, <code>status</code></li>
<li>Sets/updates posts by slug; supports <code>publish</code>, <code>draft</code>, <code>pending</code></li>
</ul>


GrowthSEO – Content Sync

Secure REST endpoint to publish posts from GrowthSEO backend via API key.

danielauener

<p>This plugin adds a couple of extensions to the WordPress Rest API, which are aimed to make the use of WordPress as headless CMS easier.<br />
It is originally coded for <a href="https://github.com/northosts/wuxt" rel="nofollow ugc">WUXT</a>, a dockerized development environment for headless WordPress combined with NuxtJs. However, it can be used by every other application, which needs a powerful headless WordPress back-end.</p>
<h3>WordPress API Extensions</h3>
<ul>
<li><strong>Frontpage endpoint</strong>: There is no obvious way to get the WordPress front-page via the Rest API. To read the settings, you have to be authorized, which makes things unnecessary complicated. The new endpoint returns the front-page object if it is set, the ten newest posts otherwise.</li>
<li><strong>Menu endpoint</strong>: Right now, there is no way I know of, for getting menus from the API. This endpoint returns an entire menu as nested array. Default location is “main”, but you can request other locations.</li>
<li><strong>Slug endpoint</strong>: If you are building a front-end app on top of WordPress, you have to think about how to structure your urls. WordPress has two default post-types (posts & pages) and in the urls is not distinguished which type you are requesting, so http://wp-site.expl/something might lead to a page or a post, dependent on the type of the object with the slug something. If you want to mirror that behaviour in your app, you have to do two requests for each url, one searching pages, one searching posts. To make that one request, use the slug end-point.</li>
<li><strong>Taxonomy filter AND extension</strong>: When filtering taxonomies with an Rest API request, all queries are OR-queries. That means you can get posts which are either in category A or B. Our adjustment lets you switch all tax_queries to an AND-relation, so that you can select posts which are both in category A and B.</li>
<li><strong>Geo query</strong>: If your application has to get posts by geographical proximity, you can use a geo query.</li>
<li><strong>WordPress SEO meta fields</strong>: They are included automatically in the <code>meta</code> object if the Yoast WordPress SEO plugin is activated.</li>
<li><strong>Advanced custom fields</strong> are included automatically in the <code>meta</code> object if the plugin is activated.</li>
</ul>
<h3>Endpoints and parameters</h3>
<p><strong>Frontpage</strong></p>
<ul>
<li><code>GET</code> <code>/wp-json/wuxt/v1/front-page</code></li>
<li><code>GET</code> <code>/wp-json/wuxt/v1/front-page?_embed</code></li>
</ul>
<p><strong>Menu</strong></p>
<ul>
<li><code>GET</code> <code>/wp-json/wuxt/v1/menu</code></li>
<li><code>GET</code> <code>/wp-json/wuxt/v1/menu?location=<location></code></li>
</ul>
<p><strong>Slug</strong></p>
<ul>
<li><code>GET</code> <code>/wp-json/wuxt/v1/slug/<post-or-page-slug></code></li>
<li><code>GET</code> <code>/wp-json/wuxt/v1/slug/<post-or-page-slug>?_embed</code></li>
</ul>
<p><strong>Taxonomy filter AND extension</strong></p>
<ul>
<li><code>GET</code> <code>/wp-json/wp/v2/posts/?categories=1,2&and=true</code></li>
</ul>
<p><strong>GEO query</strong></p>
<ul>
<li><code>GET</code> <code>/wp-json/wp/v2/posts/?coordinates=<lat>,<lng>&distance=<distance><km|m></code></li>
<li><code>GET</code> <code>/wp-json/wp/v2/posts/?coordinates=<lat_meta_field>:<lat>,<lng_meta_field>:<lng>&distance=<distance><km|m></code></li>
<li><code>GET</code> <code>/wp-json/wp/v2/posts/?coordinates=52.585,13.373&distance=10</code></li>
<li><code>GET</code> <code>/wp-json/wp/v2/posts/?coordinates=lat_mkey:52.585,lng_mkey:13.373&distance=10</code></li>
<li><code>GET</code> <code>/wp-json/wp/v2/posts/?coordinates=52.585,13.373&distance=10m</code></li>
</ul>
<h3>Links</h3>
<ul>
<li><a href="https://www.danielauener.com/wordpress-rest-api-extensions-for-going-headless-wp/" rel="nofollow ugc">More detailed end-point description</a></li>
<li><a href="https://github.com/northosts/wuxt" rel="nofollow ugc">WUXT</a></li>
<li><a href="https://www.danielauener.com/nuxt-js-wordpress-wuxt/" rel="nofollow ugc">WUXT release blog post</a></li>
<li><a href="https://nuxtjs.org/" rel="nofollow ugc">NuxtJs</a></li>
</ul>
<h3>Credits</h3>
<ul>
<li>Michael Cox <a href="https://gist.github.com/michaeland/191ce08d22fed74da05a" rel="nofollow ugc">Menu Class for returning a menu as array</a></li>
</ul>


WUXT Headless WordPress API Extensions

Extensions for the Rest API to provide endpoints that support a more convenient use of headless WordPress as back-end CMS.

GrowthSEO – Content Sync vs WUXT Headless WordPress API Extensions