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

Internal changes

Endpoints will take a single parameter, as opposed to the previous version. The endpoint in question is WP_REST_Request. The argument registration has been transferred to route registration, and argument options are set to a default value.

  • Register_rest_route will now help with route registration, but requires the use of a namespace. It is used with the plugin slug along the plugin version like so wp/v2.

  • Built-in endpoints will now make use of a typical controller base class, which has its standardized pattern. In version 2, this changed to become a public API for developers, and the recommendation is that this is applied when working with most use cases. While it is not mandatory in custom code, it will just embody best practices in the core of the API.

  • Callbacks with permissions will now be registered in a separate manner towards the response callback, which will allow better capability assertions for clients.

  • The server will now sanitize and validate arguments for us by...