renemanqueros

<p>Allows developers to create REST-ish API’s that have access to all of WordPress and its plug-ins objects.</p>
<h3>Usage</h3>
<p>Install the plug-in as any other plug-in.<br />
Project is divided in two sets of files:</p>
<pre><code>* index.php - This is where you register routes and/or middleware.
* routes/ - This is where you place your routes.
</code></pre>
<h3>Middleware</h3>
<p>Middlewares are functions that will be executed on every call to the API, generally used to validate parameters or<br />
transform requests before they reach routes, code for middleware is structured like this:</p>
<pre><code>app::middleware(function () {
    doSomething();
});
</code></pre>
<ul>
<li>Middlewares run for every Verb and do not automatically assign $_POST or $_GET to any variable</li>
</ul>
<h3>Routes</h3>
<p>A route is where you would link a request to a function depending on its HTTP Verb.<br />
The routing engine will prepend /api/ to all calls and will append a trailing slash to all requests.<br />
A GET request would be matched like this:</p>
<pre><code>app::get('/testget', function($req){
   return $req;
});
</code></pre>
<p>In which:</p>
<pre><code>* app::get - This will match up a GET request.
* '/testget' - the path the routing engine will look for.
* function(){ } ... - the function to execute when the route is matched.
* $req - parameters sent to the verb.
</code></pre>
<p>To make a call to this route, the full path would be:</p>
<pre><code>http://www.mysite.com/api/testget/
</code></pre>
<ul>
<li>The trailing slash is always required.</li>
<li>Parameters for all routes will be sent as the first parameter to the callback.</li>
</ul>
<p>A route should be registered on the index file by placing a call to app::routes with the filename of the route (without the extension) as a parameter:</p>
<pre><code>app::routes('test');
</code></pre>
<ul>
<li>All routes output their return value as a JSON encoded response.</li>
</ul>
<h3>Samples for all verbs</h3>
<ul>
<li>
<p>GET:</p>
<p>app::get(‘/testget’, function($req){<br />
   return $req;<br />
});</p>
</li>
<li>
<p>POST:</p>
<p>app::post(‘/testpost’, function($req){<br />
    return $req;<br />
});</p>
</li>
<li>
<p>DELETE:</p>
<p>app::delete(‘/testdelete’, function($req){<br />
    return $req;<br />
});</p>
</li>
<li>
<p>PUT:</p>
<p>app::put(‘/testput’, function($req){<br />
    return $req;<br />
});</p>
</li>
</ul>
<h3>Nested routes</h3>
<p>Routes can be nested like this:</p>
<pre><code>app::delete('/admin/machines', function($req){
    return $req;
});
</code></pre>
<p>Which could be called by issuing a DELETE to:</p>
<pre><code>http://www.mysite.com/api/admin/machines/<h3>Route and middleware registration</h3>
Code for the routes should be placed on a file inside the "routes" folder and then "registered" on the index.php file like this:
</code></pre>
<p>function gp_registerapimethods()<br />
{<br />
    app::middleware(function () {</p>
<pre><code>});

app::routes('test');
</code></pre>
<p>}</p>
<p>Only one instance of the gp_registerapimethods should exist on the index.php file.<br />
Middleware and Routes can have as many instances as needed.<br />
All routes inside the routes folder can be registered by doing this call instead of the individual route registration:</p>
<pre><code>  app::routes('*');
  <h3>Sample for everything</h3> The index.php file has the "test" route registered, and that test.php route a call for each verb which you could use as a starting point for your own services.
</code></pre>


GP routing – WP compatible REST API

Allows developers to create REST-ish API's that have access to all of Wordpress and its plug-ins objects.

berkux

<p>The simplest method to link WordPress with external APIs</p>
<p>JCI simplifies the task of retrieving data from a third-party REST API. The returned JSON-, XML, CSV, TXT-data can be neatly arranged and showcased on your WordPress site via a shortcode, a JCI Block or PHP. The plugin can generate a template for the data display.</p>
<p>20 seconds: Load API and display data</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/RBlrAUVywAk?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<p>7 minutes: Basic intro to JCI free</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/SDUj1teNG2s?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h3>Examples, Preview</h3>
<p>Check out the live demonstration to explore how we’re interfacing with various APIs<br />
<a href="https://api.json-content-importer.com/free-jci-plugin-example/wetter/" rel="nofollow ugc">LIVE PREVIEW – WordPress and a external API</a></p>
<p><a href="https://www.youtube.com/watch?v=GJGBPvaKZsk" rel="nofollow ugc">Video: How to use the Wikipedia API</a></p>
<h3>Main Plugin Features</h3>
<ul>
<li>Low code usage: Save time and avoid coding using an API</li>
<li>Insert an API-URL into Step 1: Data is loaded, and and displayed. Save it as API-Access-Set.</li>
<li>Use the API-Access-Set in Step 2 to create a Shortcode</li>
<li>Optional for maximum flexibility: Use the API-Access-Set n PHP code</li>
<li>Insert an API-URL into the JCI Block: Data is loaded, and a template can be generated to display the data.</li>
<li>Easy to start: Check Installation – Is your WordPress ready for JCI? Most probably!</li>
<li>Basic Settings: Check SSL, Cacher, Gutenberg and Authentication</li>
<li>ContactForm7 Integration: Populate CF7 forms with JSON data and forward CF7-submitted data to an API.</li>
<li>Use the JCI cacher to avoid many API requests</li>
<li>JCI-Block :  Use the simple JCI Block interface to get data! Query the API and check the response. Then utilize the simple template generator inside the JCI Block to use the data!</li>
<li>Contact Form 7 Integration: Fill form and submit to API</li>
</ul>
<h3>Documentation</h3>
<p>There’s a wealth of resources and support at your fingertips. Explore the articles listed below to begin your journey:</p>
<ul>
<li><a href="https://doc.json-content-importer.com/" rel="nofollow ugc">JCI Manual</a></li>
<li><a href="https://doc.json-content-importer.com/json-content-importer/step-1-data-access/" rel="nofollow ugc">Step 1: Access the Data</a></li>
<li><a href="https://doc.json-content-importer.com/json-content-importer/step-2-data-usage/" rel="nofollow ugc">Step 2: Using the Data</a></li>
<li><a href="https://doc.json-content-importer.com/json-content-importer/shortcode-basic-structure/" rel="nofollow ugc">Shortcode – Basic structure</a></li>
<li><a href="https://doc.json-content-importer.com/json-content-importer/pro-contactform7/" rel="nofollow ugc">Contact Form 7 Integration</a></li>
<li><a href="https://doc.json-content-importer.com/json-content-importer/free-overview-videos/" rel="nofollow ugc">Free JCI Plugin: Overview Videos</a></li>
<li><a href="https://doc.json-content-importer.com/json-content-importer/basic-start/" rel="nofollow ugc">Free JCI Plugin: Getting Started</a></li>
</ul>
<h3>You need more?</h3>
<h4>JSON Content Importer PRO</h4>
<p>Both the free and PRO JCI Plugins serve the same purpose: retrieving data, transforming it, and publishing the results.<br />
However, while the free Plugin can only handle basic challenges, the PRO JCI Plugin offers nearly full control over WordPress, the database, and applications.<br />
<a href="https://json-content-importer.com/compare/" rel="nofollow ugc">Compare: Free vs. JCI PRO Plugin</a></p>
<p>PRO features:<br />
* application building by creating a searchform and connect it to a JSON-API in the background: pass GET-Variables to use a dynamic JSON-Feed-URL (“talk to API / webservice”)<br />
* much better and more flexible templateengine: twig<br />
* create and use Custom Post Types<br />
* store Templates independent of pages<br />
* more Shortcode-Parameters<br />
* executing Shortcodes inside a template<br />
* more features…</p>


Get Use APIs – JSON Content Importer


All I wanted to do is display the latest version number of my own plugin on my site.  I could have spent hours coding it myself, instead I spent 5 minutes installing and working out this plugin.  Great work Bernhard


Easy Peasy


learning curve is very steep with the plugin but it simply works and i fell in love with it! i use it for everything: fetching flight prices, weather data, syncing wordpress blocks / content across different sites / domain through wp rest api to name a few!


such a clever plugin

Connects an API to WordPress: Get API-data (JSON, XML, CSV...), show it with a Shortcode, a JCI Block or PHP. Generate a template with the JCI Block

GP routing – WP compatible REST API vs Get Use APIs – JSON Content Importer