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

Custom API tokens

Authentication based on tokens has been around for quite a while and rightfully, given the common use of APIs, tokens have proved to be one of the best ways of handling authentication for a bunch of users. While there are other means of authentication, the main features that this authentication provides are that it is mobile-application ready, and has improved security and extensive scalability which when it works as implied is more than enough for smooth authentication. Any significant web application that you might have used, like any social media hub, makes use of token-based authentication and we will go through the reasons why they took that path. Given that the protocol of HTT (HTTP) is stateless, the authentication of a user just with his credentials will not produce any result, as these details wouldn't have anything to be paired with to confirm the authentication, which is why user information is stored server-wide and is used whenever somebody makes a request...