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.

David Anderson / Team Updraft

Prashant Baldha

DNutbourne

aporter

Venkat Raj

WPGetAPI

<p>Connect WordPress to external APIs, without code.</p>
<p>Easily send data to any API and get data from unlimited 3rd party REST APIs. Format and display the returned data on your WordPress website using a shortcode or a template tag.</p>
<p><iframe loading="lazy" title="Quick intro to WPGetAPI" width="750" height="422" src="https://www.youtube.com/embed/X50qINEs1yo?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></p>
<p>WPGet API supports virtually all authentication methods including API keys, bearer tokens, basic auth, username/password and <a href="https://wpgetapi.com/downloads/oauth-2-0-authentication/?utm_campaign=OAuth&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">OAuth 2.0 authorization</a>.</p>
<h3>Live Examples</h3>
<p>View our live examples of connecting to several different APIs and displaying the data in various unique ways including charts, graphs, tables and weather forecasts.</p>
<p><a href="https://wpgetapi.com/demo-connecting-wordpress-to-external-api/?utm_campaign=Demo&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">LIVE EXAMPLES – Connecting WordPress to external APIs</a></p>
<h3>Major Features</h3>
<ul>
<li>Connect your WordPress website to any REST API</li>
<li>Unlimited APIs & endpoints</li>
<li>No coding required</li>
<li>Display API data using a template tag or shortcode</li>
<li>GET, POST, PUT, PATCH & DELETE methods</li>
<li>Add query string, header & body parameters</li>
</ul>
<h3>Documentation</h3>
<p>We have tons of articles and help available.</p>
<ul>
<li><a href="https://wpgetapi.com/docs/quick-start-guide/?utm_campaign=Docs&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">Quick Start Guide</a></li>
<li><a href="https://wpgetapi.com/docs/step-by-step-example/?utm_campaign=Docs&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">Step by Step Example</a></li>
<li><a href="https://wpgetapi.com/docs/frequently-asked-questions/?utm_campaign=Docs&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">Frequently Asked Questions</a></li>
<li><a href="https://wpgetapi.com/docs/will-this-work-with-my-api/?utm_campaign=OAuth&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">Will this work with my API?</a></li>
</ul>
<h3>Extending WPGet API</h3>
<h4>PRO Plugin</h4>
<p>The <strong><a href="https://wpgetapi.com/downloads/pro-plugin/?utm_campaign=Pro&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">PRO Plugin</a></strong> provides many extra features that allow you to do some more advanced things with your APIs. Features of the PRO Plugin include:</p>
<ul>
<li>Actions – automate your API when an action happens on your site</li>
<li>Tokens – grab dynamic data without code and send to your API</li>
<li>Dynamic variables – a PHP solution for grabbing dynamic values</li>
<li>Chain API calls</li>
<li>Cache API calls</li>
<li>Format API data into HTML</li>
<li>Retrieve nested data</li>
<li>Base64 encoded auth</li>
<li>XML format</li>
</ul>
<h4>API to Posts Plugin</h4>
<p>The <strong><a href="https://wpgetapi.com/downloads/api-to-posts/?utm_campaign=APItoPosts&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">API to Posts Plugin</a></strong> allows you to import API data and create WooCommerce products or custom posts from this API data. Features of the API to Posts Plugin include:</p>
<ul>
<li>Import API data</li>
<li>Import from unlimited endpoints</li>
<li>Map API data to WordPress fields</li>
<li>Supports custom fields, ACF, tags, categories, custom taxonomies, images and more</li>
<li>Supports all standard WooCommerce fields</li>
<li>Create WooCommerce products from API data</li>
<li>Sync API to WooCommerce products & posts</li>
<li>Set interval of sync from every minutes up to once a week</li>
</ul>
<h4>OAuth 2.0 Authorization</h4>
<p>The <strong><a href="https://wpgetapi.com/downloads/oauth-2-0-authentication/?utm_campaign=OAuth&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">OAuth 2.0 Authorization</a></strong> plugin allows authorization of your API through the OAuth 2.0 method.</p>
<h3>WPGet API Integrations</h3>
<p>WPGet API integrates extremely well with other WordPress plugins, allowing you to do some very cool things with your API. Click the links below for more info on these integrations.</p>
<ul>
<li><a href="https://wpgetapi.com/docs/connect-woocommerce-to-api/?utm_campaign=Integrations&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">WooCommerce to API</a></li>
<li><a href="https://wpgetapi.com/docs/woocommerce-api-product-sync/?utm_campaign=Integrations&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">WooCommerce API Product Sync</a></li>
<li><a href="https://wpgetapi.com/docs/send-contact-form-7-data-to-api/?utm_campaign=Integrations&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">Contact Form 7 send data to API</a></li>
<li><a href="https://wpgetapi.com/docs/send-wpforms-data-to-api/?utm_campaign=Integrations&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">WPForms send data to API</a></li>
<li><a href="https://wpgetapi.com/docs/send-gravity-forms-data-to-api/?utm_campaign=Integrations&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">Gravity Forms send data to API</a></li>
<li><a href="https://wpgetapi.com/docs/using-with-wpdatatables/?utm_campaign=Integrations&utm_medium=wporg&utm_source=readme" rel="nofollow ugc">Charts & Tables from API data using wpDataTables</a></li>
</ul>
<h3>Translating WPGet API</h3>
<p>You can translate WPGet API into your own language on <a href="https://translate.wordpress.org/projects/wp-plugins/wpgetapi/" rel="nofollow ugc">translate.wordpress.org</a></p>
<p>Here is an article to help <a href="https://make.wordpress.org/polyglots/handbook/translating/first-steps/" rel="nofollow ugc">get started with translations</a></p>


WPGet API – Connect to any external REST API

Connect any REST API to WordPress. WPGet API enables easy API integration, allowing you to display API data without any code.

GP routing – WP compatible REST API vs WPGet API – Connect to any external REST API