Sunil Kumar

Apitect API Feed Display lets you connect to any external REST API or XML feed and display the response data anywhere on your WordPress site — no coding required.
Key Features:
<ul>
<li>Admin Endpoint Manager — Add, edit, delete, and live-test saved API endpoints</li>
<li>JSON & XML Support — Auto-detect or manually specify the response format</li>
<li>Response Caching — Configurable TTL using the WordPress Transients API</li>
<li>4 Display Modes — Table, Cards, List, or Raw JSON</li>
<li>Shortcode — <code>[apitect_feed]</code> with rich attribute support</li>
<li>Sidebar Widget — Display any saved endpoint in any widget area</li>
<li>Gutenberg Block — Drag-and-drop block with live editor preview</li>
<li>Custom HTTP Headers — Bearer tokens, API keys, and custom headers per endpoint</li>
<li>Data Path Drilling — Dot-notation to target nested data (e.g. <code>data.items</code>)</li>
<li>Field Filtering — Show only specific keys from the response</li>
<li>Item Limiting — Restrict the number of rows or cards displayed</li>
</ul>
<h3>External Services</h3>
This plugin connects to external APIs and services that you configure yourself. No external service is contacted by default — connections only occur when you explicitly add an endpoint URL in the plugin’s admin settings and that endpoint is requested on your site.
What data is sent: 
The plugin makes HTTP requests (GET, POST, etc.) to the API URLs you configure. The request may include any custom HTTP headers you specify (such as API keys or Bearer tokens). No data is sent to any third-party service by Apitect API Feed Display itself — all API calls go directly to the URL you enter.
When data is sent: 
A request is made to your configured API URL when: 
– A page/post containing the <code>[apitect_feed]</code> shortcode or the Gutenberg block is loaded by a visitor. 
– You use the “Test” button in the admin panel to preview a response. 
– A sidebar widget configured with an endpoint is displayed.
Responses are cached using WordPress Transients to reduce repeated API calls (configurable per endpoint; default 300 seconds).
Third-party API policies: 
You are solely responsible for ensuring that your use of any external API complies with that service’s terms of service and privacy policy. Please review the terms and privacy policy of any API you connect to:
<ul>
<li>The plugin has no affiliation with any external API provider.</li>
<li>API providers may log IP addresses, request metadata, or other information per their own policies.</li>
<li>For APIs that handle personal data, ensure you have appropriate disclosures in your site’s own Privacy Policy.</li>
</ul>
<h3>Shortcode Reference</h3>
Basic usage: 
 [apitect_feed id=”my-endpoint”]
With options: 
 [apitect_feed id=”my-endpoint” display=”card” limit=”5″ fields=”id,name,email” title=”Users”]
Ad-hoc URL (no saved endpoint needed): 
 [apitect_feed url=”https://jsonplaceholder.typicode.com/users” format=”json” display=”table”]
Available attributes:
<ul>
<li><code>id</code> — ID of a saved endpoint</li>
<li><code>url</code> — Ad-hoc API URL (used when no <code>id</code> is provided)</li>
<li><code>method</code> — HTTP method, default <code>GET</code></li>
<li><code>format</code> — <code>auto</code>, <code>json</code>, or <code>xml</code> (default <code>auto</code>)</li>
<li><code>cache_ttl</code> — Cache duration in seconds, default <code>300</code> (0 = disabled)</li>
<li><code>display</code> — <code>table</code>, <code>card</code>, <code>list</code>, or <code>raw</code> (default <code>table</code>)</li>
<li><code>path</code> — Dot-notation path into the response, e.g. <code>data.items</code></li>
<li><code>limit</code> — Maximum number of items to show (0 = all)</li>
<li><code>fields</code> — Comma-separated list of keys to display</li>
<li><code>title</code> — Optional heading rendered above the output</li>
</ul>

Apitect API Feed Display

Fetch, cache, and display data from any external REST API or XML source via shortcode, sidebar widget, or Gutenberg block.

relisiuol

Content Aggregator helps WordPress sites import external content as posts. It is built for sites that need to pull from feeds or remote endpoints on a schedule, while still controlling how imported posts are titled, dated, categorized, and published.
Out of the box, Content Aggregator includes parser definitions for RSS feeds, Atom feeds, and WordPress REST API post endpoints. Its parser registry uses JSON and XML mappings, so additional source formats can be supported without changing the import workflow.
<h3>Key features</h3>
<ul>
<li>Manage import sources from the WordPress admin.</li>
<li>Detect the source type automatically from a source URL.</li>
<li>Import new items through WP-Cron on a configurable schedule.</li>
<li>Limit how many sources are checked during each scheduled run.</li>
<li>Configure post title, date, and content templates with placeholders.</li>
<li>Assign categories and choose the post status for imported content.</li>
<li>Set a default featured image when the remote item has no usable image.</li>
<li>Avoid duplicate imports using the original item URL.</li>
<li>Optionally enforce unique post titles.</li>
<li>Optionally redirect imported posts to the original source URL.</li>
<li>Configure the request User-Agent and SSL certificate path for remote fetches.</li>
<li>Automatically disable sources that stay offline beyond the configured expiration delay.</li>
</ul>
<h3>Supported sources</h3>
Content Aggregator ships with support for common feed and WordPress content sources:
<ul>
<li>RSS feeds.</li>
<li>Atom feeds.</li>
<li>WordPress REST API post endpoints.</li>
<li>JSON and XML sources when a matching parser definition is available.</li>
</ul>
<h3>Imported post templates</h3>
Each source can define templates for the imported post title, publication date, and content. Templates can use placeholders for the original title, source name, current import date, original publication date, original content, and original URL.

Content Aggregator

Create WordPress posts from RSS, Atom, WordPress REST API, JSON, and XML sources.

Apitect API Feed Display vs Content Aggregator