This article is about the cool feature WordPress core has – the REST API support and the plugins that deal with it in different ways.
- REST API Use Cases
- JetEngine (Premium)
- WPGetAPI (Freemium)
- JSON Content Importer (Freemium)
- Custom Endpoints for API (Premium)
- 4 Free Add-Ons for WordPress REST API
- FAQ
- Conclusion
REST API Use Cases
In simple terms, REST API is a protocol of communication between APIs. WordPress started supporting the REST API by default from version 4.7, released in 2016. This version introduced the core infrastructure for the REST API endpoints, making it possible to interact with WordPress data using standard HTTP methods. Since then, the REST API has been continuously improved and expanded upon in subsequent WordPress releases, with new features, endpoints, and enhancements added to provide developers with more flexibility and capabilities in building applications on top of WordPress. The data is being sent and received as JSON.
REST API is a developer-oriented feature of WordPress but can be used for much simpler tasks, such as collecting data from various sources on one website, as described here.
However, here are the examples of more advanced usage of this protocol:
- Headless WordPress websites. Headless structure decouples the front end from the backend, enabling front-end frameworks to consume WordPress content dynamically.
- Mobile App integration. Using REST API, the mobile app connects to the WordPress backend to retrieve content and user data.
- External service integration. REST API enables integration between WordPress and external systems, such as CRMs or eСommerce platforms, for data synchronization and user authentication.
- Custom dashboard and administrative interfaces. Such functionality enables communication between custom front-end interfaces and the WordPress backend, improving the management of content, settings, and user accounts. For instance, the WordPress.com dashboard Calysto communicates with the WordPress core using REST API.
- Data migration and synchronization. REST API functionality is crucial for migrating content between WordPress sites or synchronizing data with external databases.
- Custom applications and web services. REST API allows developers to build custom web applications or services that interact with WordPress programmatically, retrieving content and updating data through REST API endpoints.
The use cases listed above are mostly for developers, and the data manipulation should be done with the help of code. Still, the main topic of this article is plugins that help users deal with REST API endpoints. The main use cases for it are fetching content from remote sources and posting it to the remote sources using front-end inputs (forms) or dealing with endpoints, their visibility, and security.
So, let’s focus on such plugins and what they can offer.
JetEngine (Premium)
🏆 Best for displaying content from remote sites.
JetEngine offers an elaborate functionality for dealing with REST API endpoints and the unique feature of fetching and displaying data from remote sources using a visual interface, so you don’t have to dive into coding. You simply create a listing template and choose the REST API endpoint as a source. Also, you can fetch the remote posts as single pages. Check the detailed guide on use cases here.
Key features:
- REST API toolset is one of the JetEngine’s modules and can be switched off if you don’t use it;
- visual interface;
- a complete functionality for displaying remote content without coding.
Pricing: $43/year for the plugin with all the modules included.
Pros:
- complete toolset for working with REST API endpoints;
- endpoints for posts, CPTs, CCTs, and even custom query results (unique, powerful feature);
- very easy-to-use interface;
- the unique functionality for fetching and displaying remote content without coding;
- doesn’t require third-party services, such as Postman;
- CCT entity specifically adjusted for dealing with endpoints;
- smooth integration with JetFormBuilder forms;
- caching and authorization settings;
- the plugin is extremely cheap for what it offers.
Cons: not detected.
WPGetAPI (Freemium)
🏆 Best for event-driven posting on remote sites.
This plugin enables dealing with REST API endpoints to retrieve and post data as well as other manipulations with remote content. The interface is quite straightforward; however, it requires some coding skills to format the fetched content.
Key features:
- unlimited APIs;
- the output comes as a shortcode;
- settings for query parameters and headers.
Pricing: free; $89/year for one site.
Pros:
- quite powerful functionality;
- a free version is available;
- the Pro version has a list of event triggers.
Cons:
- it requires writing PHP code to format the content;
- to display WooCommerce products, create listings, or use authorization, the extra add-ons are required, with the price of $89-165 for one site;
- no caching;
- not much documentation, and half of the links didn’t work when I tried to read the docs.
JSON Content Importer (Freemium)
🏆 Best for fetching whole pages.
This plugin is better to be called Pro because this is where it has most of the functionality. However, there’s also a free version, and it’s not only limited but also has a different approach and tools to work with it.
The free version is for fetching data from remote sources and uses the Gutenberg block with all the settings directly in the editor or a shortcode with editable parameters. For content formatting, there’s a markup syntax.
The Pro version offers much more flexible settings, POST/PUT methods, Twig formatting (so some PHP can be added to the templates as well), third-party plugin integrations, etc.
Key features:
- a complete functionality for dealing with remote APIs;
- data caching;
- extra free plugins for AJAX reload and Cron plugins to extend the functionality.
Pricing: free (very limited); $59/year for one site.
Pros:
- supports data caching;
- offers a template engine, even in a free version (but it’s quite limited);
- a usage of Twig in Pro gives a lot of advantages;
- integration with custom fields plugins, Elementor, and Gutenberg;
- well-documented.
Cons:
- a bit confusing interface, which is not so easy to use;
- the user of this plugin should definitely have some coding skills.
Custom Endpoints for API (Premium)
🏆 Best for those who need endpoints for SQL queries.
I classify this plugin as Premium, even though there’s a free version, but it’s extremely limited. For the proper functionality, you will need not only the Enterprise plan of the plugin but probably a couple of other plugins from the same developer.
Key features:
- full functionality is on the Enterprise plan;
- SQL queries to endpoints functionality;
- OAuth 2.0 support.
Pricing: $245/year for one site for the Enterprise plan (the one with full functionality), plus the support costs starting at $99 a year.
Pros:
- sandbox to test a plugin;
- SQL queries to endpoints;
- a user-friendly interface;
Cons:
- it can get very expensive;
- the developer slices the functionality to small paid plugins, so you will most likely need and settle for more items, not to mention the paid tech support.
4 Free Add-Ons for WordPress REST API
These plugins are very useful, but they do more of a service job; that’s why I put them on a separate list.
WP REST API Controller
This plugin does exactly what its name suggests: it controls the visibility of endpoints the website has, supporting all the existing custom post types and meta keys. In addition, you can edit meta keys’ names to be used in the API requests. The plugin also supports taxonomies.
Pros and Cons: a very easy-to-use interface, and the name editor is a cool feature.
WP REST Cache
Communication using REST API means HTTP requests, so it can become an issue for the website’s performance. Luckily, there’s a way to cache endpoints to improve this situation. And this plugin is made exactly for this.
It has quite a comprehensive functionality, supports not only default but custom endpoints for posts and taxonomies, and you can specify the cache time-outs, flash it manually, and even see the number of times the cache has been retrieved.
Pros and Cons: a great plugin for what it is made for; no cons detected.
JWT Authentication for WP REST API
JWT tokens not only improve security but are also good for performance and scalability, passing users’ credentials and roles and using HTTP Authorization headers for this sake.
Pros and Cons: a great plugin for developers.
WP-REST-API V2 Menus
The plugin adds new routes for menus, as simple as that. It can be very useful for certain projects.
Pros and Cons: the only issue is that this plugin is not being frequently updated.
FAQ
API calls in a RESTful API refer to the interactions between a client (such as a web browser, mobile app, or other software) and a server that hosts the API.
Endpoint caching is a technique used to improve the performance of REST API endpoints by storing the responses of these endpoints temporarily. When a client makes a request to a cached endpoint, the server checks if a cached response exists and, if so, returns the cached response instead of processing the request again.
Use {your-site.com}/wp-json/wp/v2/{resource-endpoint}. Examples of “resource-endpoint” are posts, comments, users, etc. For instance, the {your-site.com}/wp-json/wp/v2/posts will show posts, and {your-site.com}/wp-json/wp/v2/films – a CPT named “films.”
Conclusion
REST API is a powerful tool, great for custom development. However, dealing with it using a plugin can be a superb solution if we talk about connecting two sites, collecting data from forms, etc.
- JetEngine is definitely one of the most user-friendly and comprehensive solutions in this list, as well as the cheapest, not to mention that REST API functionality is just one of the modules it provides.
- JSON Content Importer is a nice option with a pretty functional free version if you need to fetch some chunks of content.
- WPGetAPI is good for event-driven API calls.
- Custom Endpoints for API is a solution if you want to display custom SQL queries as endpoints.
The rest of the plugins can be great supporting tools when dealing with REST API.
