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

Competing architectures on the Web

As a group of web services, it is important to outline the competition that is happening between three main services, which are RESTful services, the RPC-style ones, and the combination of these two, which are hybrid REST-RPC combinations.

RESTful architectures

Our main concern is the RESTful web service architectures, which is why we will start with an overview of them. Within the architectures of the RESTful systems, information goes straight to the HTTP method, while in resource-oriented architectures, the information goes into the URL. Within the first line of the request sent to HTTP to a resource-oriented RESTful web service lies the info about the desire of the client. The remaining details can be made with one line of code and if the HTTP method does not correspond with the method information, then it is to be considered that the service is not a RESTful one and if the information isn't within the URI, the service will correspondingly not be thought...