wp-api/wp-api

Access your WordPress site's data through an easy-to-use HTTP REST API.

REST API

Access your WordPress site's data through an easy-to-use HTTP REST API., _(*1)

, _(*2)

About

WordPress is moving towards becoming a fully-fledged application framework, and we need new APIs. This project was born to create an easy-to-use, easy-to-understand and well-tested framework for creating these APIs, plus creating APIs for core., _(*3)

This plugin provides an easy to use REST API, available via HTTP. Grab your site's data in simple JSON format, including users, posts, taxonomies and more. Retrieving or updating data is as simple as sending a HTTP request., _(*4)

Want to get your site's posts? Simply send a GET request to /wp-json/posts. Update user with ID 4? Send a POST request to /wp-json/users/4. Get all posts with the search term "awesome"? GET /wp-json/posts?filter[s]=awesome. It's that easy., _(*5)

WP API exposes a simple yet easy interface to WP Query, the posts API, post meta API, users API, revisions API and many more. Chances are, if you can do it with WordPress, WP API will let you do it., _(*6)

WP API also includes an easy-to-use Javascript API based on Backbone models, allowing plugin and theme developers to get up and running without needing to know anything about the details of getting connected., _(*7)

Check out our documentation for information on what's available in the API and how to use it. We've also got documentation on extending the API with extra data for plugin and theme developers!, _(*8)

We're currently aiming for integration into WordPress 4.1 as a permanent part of core., _(*9)

Installation

Drop this directory in and activate it. You need to be using pretty permalinks to use the plugin, as it uses custom rewrite rules to power the API., _(*10)

Quick Setup

Want to test out WP-API and work on it? Here's how you can set up your own testing environment in a few easy steps:, _(*11)

1. Install Vagrant and VirtualBox.

2. Clone Chassis:, _(*12)

   git clone --recursive git@github.com:Chassis/Chassis.git api-tester
   

3. Grab a copy of WP API:, _(*13)

   cd api-tester
   mkdir -p content/plugins content/themes
   cp -r wp/wp-content/themes/* content/themes
   git clone git@github.com:WP-API/WP-API.git content/plugins/json-rest-api
   

4. Start the virtual machine:, _(*14)

   vagrant up
   

5. Activate the plugin:, _(*15)

   vagrant ssh -c 'cd /vagrant && wp plugin activate json-rest-api'
   

6. Set the permalink structure to something other than the default, in order to enable the http://vagrant.local/wp-json/ endpoint URL (if you skip this step, it can be accessed at http://vagrant.local/?json_route=/):, _(*16)

   vagrant ssh -c "cd /vagrant && wp rewrite structure '/%postname%/'"
   

You're done! You should now have a WordPress site available at http://vagrant.local; you can access the API via http://vagrant.local/wp-json/, _(*17)

To access the admin interface, visit http://vagrant.local/wp/wp-admin and log in with the credentials below:, _(*18)

Username: admin Password: password, _(*19)

Testing

For testing, you'll need a little bit more:, _(*20)

1. Clone the Tester extension for Chassis:, _(*21)

   # From your base directory, api-tester if following the steps from before
   git clone --recursive https://github.com/Chassis/Tester.git extensions/tester
   

2. Update the wpdevel submodule in Chassis to latest on master from WordPress Git Mirror:, _(*22)

   # From your base directory, api-tester if following the steps from before
   cd extensions/tester/wpdevel
   git checkout master
   git pull
   

3. Run the provisioner:, _(*23)

   vagrant provision
   

4. Log in to the virtual machine and run the testing suite:, _(*24)

   vagrant ssh
   cd /vagrant/content/plugins/json-rest-api
   phpunit
   

   You can also execute the tests in the context of the VM without SSHing into the virtual machine (this is equivalent to the above):, _(*25)

   vagrant ssh -c 'cd /vagrant/content/plugins/json-rest-api && phpunit'
   

Issue Tracking

All tickets for the project are being tracked on GitHub. You can also take a look at the recent updates for the project., _(*26)

Previous issues can be found on the [GSOC Trac][] issue tracker, however new issues should not be filed there., _(*27)