Extends the WP-REST API with custom read only endpoints.
Author: | Lars Jensen (profile at wordpress.org) |
WordPress version required: | 4.3.1 |
WordPress version tested: | 4.3.1 |
Plugin version: | 1.0.6 |
Added to WordPress repository: | 10-11-2015 |
Last updated: | 10-11-2015
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
Rating, %: | 0 |
Rated by: | 0 |
Plugin URI: | https://github.com/larjen/WPRestApiExtensions |
Total downloads: | 803 |
Click to start download |
Extends the WP-REST API with custom read only endpoints.
If you have a WordPress blog at http://www.example.com you can reach the read only REST API by requesting these endpoints:
http://www.example.com/wp-json/wprestapiextensions/v1/posts?page=1&per_page=12&search=query&tags=tag1+tag2
http://www.example.com/wp-json/wprestapiextensions/v1/tag?tag_name=tag1
http://www.example.com/wp-json/wprestapiextensions/v1/post
The above endpoints does read from database whenever they are requested, and are thus very slow to react.
From within the plugin, there is an option to deploy a cache in front of this REST API. When you deploy it, be warned that the folder "rest-api" will be created in the root of your webserver.
You can then request the REST-API like this:
http://www.example.com/rest-api/v1/posts?page=1&per_page=12&search=query&tags=tag1+tag2
http://www.example.com/rest-api/v1/tag/?_jsonp=angular.callbacks._1&tag_name=tag1
Since these requests are infinitely cached, you can schedule an optional wipe of the cache which will occur 5 minutes after last post alteration.
FAQ
ChangeLog