Tomohiro Shiotani

<p>Content Bridge for Commerce provides a lightweight REST API endpoint that allows external commerce platforms such as Shopify to fetch WordPress editorial content.</p>
<p>This plugin does not sync databases or duplicate content. It simply exposes your WordPress posts through a clean, structured JSON API designed for external consumption.</p>
<h3>Key Features</h3>
<ul>
<li>Fetch latest WordPress posts via REST API</li>
<li>Filter posts by category or tag (using slug)</li>
<li>Return featured image, excerpt, and publish date</li>
<li>Optional conversion of Jetpack (i0.wp.com) CDN image URLs back to original URLs</li>
<li>Configurable default post count and limits</li>
<li>Built-in transient cache (5 minutes) to reduce database load</li>
<li>No data duplication or migration required</li>
</ul>
<h3>REST API Endpoint</h3>
<p>Base endpoint:</p>
<pre><code>/wp-json/content-bridge/v1/posts
</code></pre>
<p>Examples:</p>
<p>Latest posts:<br />
    /wp-json/content-bridge/v1/posts?per_page=4</p>
<p>Posts filtered by tag:<br />
    /wp-json/content-bridge/v1/posts?tax=post_tag&term=guidi&per_page=4</p>
<p>Posts filtered by category:<br />
    /wp-json/content-bridge/v1/posts?tax=category&term=news&per_page=4</p>
<p>If no taxonomy is specified, the API returns the latest posts from all published posts.</p>
<h4>Authentication</h4>
<p>This plugin protects its REST API using a simple API key mechanism.</p>
<p>Requests must include a valid API key via the following HTTP header:</p>
<p>X-Content-Bridge-Key: YOUR_API_KEY</p>
<p>If the API key is missing or invalid, the endpoint will return a 401 Unauthorized response.</p>
<p>The API key can be configured in the plugin settings screen.</p>
<p>The API key can be manually set or generated from the plugin settings screen.</p>
<h3>Settings</h3>
<p>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Content Bridge for Commerce</p>
<ul>
<li>Default number of posts</li>
<li>Maximum allowed posts per request</li>
<li>Image size (thumbnail / medium / large / full)</li>
<li>Excerpt length (word count)</li>
<li>Enable or disable Jetpack CDN URL unwrapping</li>
</ul>
<h3>Privacy</h3>
<p>Content Bridge for Commerce does not collect, store, or transmit any personal data.</p>
<p>The plugin only exposes publicly available WordPress post data (such as title, excerpt, featured image, and permalink) via a REST API endpoint.</p>
<p>No data is sent to external servers by this plugin.</p>


Content Bridge for Commerce

Bridge WordPress editorial content to Shopify and other commerce platforms via a simple REST API.

Benjamin Intal

gambitph

<p>Using WordPress entirely as a CMS (a <a href="https://medium.com/@jchiatt/headless-wordpress-with-react-d573bca02ee0" rel="nofollow ugc">Headless WordPress</a>) is a plausible option for people building web apps using technologies such as React JS or Angular JS to entirely build their front-end.</p>
<p>Doing this, the front-end (e.g. built with React) becomes decoupled from the back-end (e.g. WordPress). Since WordPress is being used strictly to manage and serve the content via REST API, the WP front-end becomes unusable and unnecessary – hence the term <em>“headless WordPress”</em>.</p>
<p><strong>This plugin essentially removes the front-end of WordPress.</strong></p>
<blockquote>
<p>Note that the REST API, and other non-front-end stuff should work as normal.</p>
</blockquote>
<h4>Features</h4>
<ul>
<li>No settings page</li>
<li>Allows backend access</li>
<li>Allows REST API endpoints</li>
<li>Redirects (403 Forbidden) all front-end pages to the login page</li>
</ul>


Redirect Front-end to Login | Headless WP

Redirects all front-end pages to the login page, best for building a headless WP REST API backend

Content Bridge for Commerce vs Redirect Front-end to Login | Headless WP