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.

WP Engine

John Parris

Chris Wiegman

Nick C

Joe Fusco

rfmeier

Anthony Burchell

markkelnar

Jason Konen

Matthew Wright

claygriffiths

Andrew Matthews

Teresa Gobble

Theo

blakewpe

Colin Murphy

<p>In conjunction with the <a href="https://www.npmjs.com/search?q=%40faustwp" rel="nofollow ugc">Faust.js™ NPM packages</a>, the Faust.js™ WordPress plugin enables a decoupled front-end to authenticate with WordPress through GraphQL mutations and REST API endpoints. It is the bridge between a Faust.js™ powered front-end application, and a WordPress backend.</p>
<p>The plugin also provides useful options for headless sites, such as the ability to:</p>
<ul>
<li>Hide “theme” admin pages.</li>
<li>Redirect public route requests to the front-end application.</li>
<li>Rewrite WordPress URLs to front-end URLs in queried content.</li>
</ul>


Faust.js

The future of headless WP


Reduces the complexity of building headless WordPress frontends for the web tenfold. Addition of Apollo helps the user flexibly perform declarative queries to manipulate and structure data too. 


Comprehensive

Faust.js™ transforms your traditional WordPress installation into a flexible headless CMS.

Content Bridge for Commerce vs Faust.js