Book Image

Learning WordPress REST API

By : Sufyan bin Uzayr, Mathew Rooney
Book Image

Learning WordPress REST API

By: Sufyan bin Uzayr, Mathew Rooney

Overview of this book

The WordPress REST API is a recent innovation that has the potential to unlock several new opportunities for WordPress developers. It can help you integrate with technologies outside of WordPress, as well as offer great flexibility when developing themes and plugins for WordPress. As such, the REST API can make developers’ lives easier. The book begins by covering the basics of the REST API and how it can be used along with WordPress. Learn how the REST API interacts with WordPress, allowing you to copy posts and modify post metadata. Move on to get an understanding of taxonomies and user roles are in WordPress and how to use them with the WordPress REST API. Next, find out how to edit and process forms with AJAX and how to create custom routes and functions. You will create a fully-functional single page web app using a WordPress site and the REST API. Lastly, you will see how to deal with the REST API in future versions and will use it to interact it with third-party services. By the end of the book, you will be able to work with the WordPress REST API to build web applications.
Table of Contents (16 chapters)
Learning WordPress REST API
About the Authors
About the Reviewer

Making sure your apps and sites are backward-compatible

The presumption has it that a REST API should always be backward compatible with a service that is being exposed to such interfaces, be those external or internal clients. In this part of our tutorial we will go through the meaning of backward compatibility and what exactly it means.

Backward compatibility implies the connection within two clients that have no conflicts of compatibility between APIs. During the report of a service to another, if the clients are not corresponding with their updates or versions of the API, then issues might arise.

It is perceived that client implementation will take some time to catch up with service implementation, thus not breaking the existing version of the API, even though it has been the subject of an upgrade. The purpose of backward compatibility implies that older clients should still work fine with a new version of the same API. While the old client will miss out the new features of the upgraded...