Beginner WordPress Developer

0 of 59 lessons complete (0%)

An introduction to the WordPress REST API

Interacting with the WordPress REST API

This is a preview lesson

Register or sign in to take this lesson.

While the WP REST API is commonly used to fetch data from WordPress, it can also be used to perform other actions.

The REST API also allows you to create, update, and delete various WordPress data types.

In this lesson, you’ll learn about the WP REST API schema, methods to authenticate a WP REST API request, tools to test WP REST API requests, as well as a couple of ways to add, edit or delete data via the WP REST API.

If you skipped the previous lessons in this module, download version 1.0.1 of the Bookstore plugin from the link in the repository readme, and install and activate the plugin on your local WordPress install.


When working with the REST API, it’s useful to keep the Endpoint Reference section of the WP REST API documentation handy. The Endpoint Reference lists all endpoints that ship with WordPress core.

Clicking on an individual endpoint, say Posts, will show you the schema for that endpoint. The schema defines all the fields that exist for a resource when fetching or creating data of that specific type.

If you’ve created a custom post type, like the books custom post type from the bookstore plugin, the schema for the custom post type endpoint will be similar to the posts endpoint.

You will notice that many of the endpoint fields match up with the fields that are available in the WordPress database table related to that data type. Some, however, are slightly different. For example, the title field for the Post endpoint will match up to the post_title field in the posts table. It is important to remember that these differences exist and to use the correct field name when interacting with the API.


By default, the WordPress REST API uses the same cookie-based Authentication method that is used when logging into the WordPress dashboard.

For any REST API endpoints that are not public, or require an authentication user to view or modify, the authentication cookie needs to be present.

This is how the block editor works, for example.

There are a number of ways to authenticate requests, including JSON Web Tokens and OAuth.

Another way that’s built into WordPress is Application passwords.

Application passwords can be set on a per-user basis, and are used to authenticate requests to the WP REST API. This allows you to let users access the API without having to share the password they use to log in to the WordPress dashboard.

To create an application password for your user, navigate to your user in the Users list, and click on the User to edit it. Scroll down to the bottom of the screen, under the Application Passwords section.

Give the new application password a name and click Add New Application Password.

The password will be generated for you. Make sure to copy it and store it somewhere securely, as you won’t be able to see it again.

In this screen you are also able to revoke the password, should it ever be leaked.

Using an application password for your user is a great way to test out REST API requests, using a REST API testing tool.

If you intend to build something more complex, like a mobile app that connects to a WordPress REST API, you should rather consider using JSON Web Tokens or OAuth 1.0a.


There are a number of tools available to test REST API requests.

For example, if you use PhpStorm, it has a built-in HTTP client, and if you use VS Code, there are extensions like There are also standalone tools like Hoppscotch, and Postman. You can even test your REST API endpoints using the curl command in your terminal.

For the purposes of this lesson, you’ll learn how to use Postman to test some REST API requests.

You can download Postman from the Postman website. By default, Postman will create an initial workspace, to store your request collections.

Once installed, open Postman, and click on the Create Collection button. This will create a new collection, where you can add multiple requests to test.

You can give the collection a name to differentiate it from other collections. Inside the collection click the Add a Request button.

This will open a new request, where you can give the request a unique name. Then, enter the URL to your local books endpoint, and click the Send button.


The request will be made, and the JSON response will be parsed and displayed in the response area.

Now, create a new request, and enter the same URL to the books endpoint, but this time change the request method to POST, and hit Send. By changing the request method to POST, you’re telling the server that you want to either create or possibly update a book.

This time you’ll be presented with an error message because you’re not authenticated.

To authenticate the request, click on the Authorization tab, and select Basic Auth from the dropdown.

Then, enter your username and the Application Password you created earlier, then click the Save button.

This time you don’t get the same error, because you’re not authenticated. So you can create books.

Go ahead and create one, by clicking on the Body tab in the request, and selecting the raw radio button. Then, select JSON from the dropdown, and enter the following JSON:

    "title": "My Postman Book",
    "content": "This is my Postman book",
    "status": "publish"

Hit send again, and the book will be created, returning the JSON response of the new book.

To be sure, go ahead and check the book in the WP dashboard, and you should see the book.

To update a book, you use the same request configuration to add a book, but you change the endpoint URL to include the book ID.

To delete a book, you use the same endpoint URL as updating a book, but you change the request method to DELETE, and don’t send any data in the request body.

You’ll also notice that deleting a post actually moves it to the trash, and doesn’t permanently delete it. This matches the behavior of the WordPress dashboard.

Using a tool like Postman to test REST API endpoints is a great way to learn how to use the WP REST API. It’s also extremely useful for testing WP REST API requests, by ensuring that the data you intend to send is formatted correctly and that the request is being made to the correct endpoint.

Creating a Book

Let’s use the WP REST API and api-fetch to create a new book.

To do so, we’ll need to pass the title and content fields as a POST request to the books endpoint.

You already have a plugin that allows you to list books, so you can use that as a starting point.

First, you’ll need to update the page with a form that will allow you to enter the title and content of the book you want to create. You can use the following HTML to create the form, and add it to the admin page callback:

<div style="width:50%;">
    <h2>Add Book</h2>
            <label for="bookstore-book-title">Book Title</label>
            <input type="text" id="bookstore-book-title" placeholder="Title">
            <label for="bookstore-book-content">Book Content</label>
            <textarea id="bookstore-book-content" cols="100" rows="10"></textarea>
            <input type="button" id="bookstore-submit-book" value="Add">

This HTML code adds a new form to the custom admin page, that allows you to enter a title and content for the new book. The form also includes a button to submit the form.

With the form added, the next step would be to add the JavaScript that will handle things when the button is clicked:

const submitBookButton = document.getElementById( 'bookstore-submit-book' );
if ( submitPostButton ) {
    submitBookButton.addEventListener( 'click', function () {
        // create post code
    } );

Now that you have the button click event listener added, you can add the code that will handle the creation of the book.

To do this, it’s a good idea to create a separate function to create the book and call that function on the click event.

The first thing you’ll need to do is create a submitBook function:

function submitBook() {
    // create book code

Then update the click event listener to call that function:

submitBookButton.addEventListener( 'click', submitBook );

Inside the submitBook function, you’ll need to get the title and content values from the form fields:

    const title = document.getElementById( 'bookstore-book-title' ).value;
    const content = document.getElementById( 'bookstore-book-content' ).value;

Now you can create the request to the books endpoint using api-fetch, by setting the path to the books endpoint, setting the request method to POST and passing the title and content as a data object:

    wp.apiFetch( {
        path: '/wp/v2/books/',
        method: 'POST',
        data: {
            title: title,
            content: content
    } ).then( ( result ) => {
        alert( 'Book saved!' );
    } );

Open the custom admin page, enter a title and content, and click the Add button. You should see an alert that says “Book saved!”.

Then, if you browse to the list of books, you’ll see your new book listed.

Updating and Deleting Books

You can also use the WP REST API to update and delete books.

You can use the same api-fetch implementation for updating items as you did for adding items. You need to update the path to include the ID of the data entity being updated (in this case books), so that it updates that item, as well as the updated data object, with the new values for the fields you want to update.

    wp.apiFetch( {
        path: '/wp/v2/books/' + id,
        method: 'POST',
        data: {
            title: newTitle,
            content: newContent
    } ).then( ( result ) => {
        alert( 'Book Updated!' );
    } );

Deleting a post only requires the path to be set to the URL of the item, and setting the method to DELETE.

    wp.apiFetch( {
        path: '/wp/v2/books/' + id,
        method: 'DELETE',
    } ).then( ( result ) => {
        alert( 'Book deleted!' );
    } );

Further Reading

For more information on creating, updating, and deleting data using the WP REST API, check out the Using the REST API of the WP REST API Handbook as well as the api-fetch package reference, in the Block Editor Handbook.