Right now, we're only registering the one endpoint for the route. ("Route" is the URL, whereas "endpoint" is the function behind it that corresponds to a method *and* a URL. For more, see the [Glossary](/glossary.html).) If your site domain is `example.com` and you've kept the API path of `wp-json`, then the full URL would be `http://example.com/wp-json/myplugin/v1/author/(?P\d+)`. Each route can have any number of endpoints, and for each endpoint, you can define the HTTP methods allowed, a callback function for responding to the request and a permissions callback for creating custom permissions. In addition you can define allowed fields in the request and for each field specify a default value, a sanitization callback, a validation callback, and whether the field is required.

The above scenario, two routes with the same name, from two different plugins, requires all vendors to use a unique namespace. Failing to do so is analagous to a failure to use a vendor function prefix, class prefix and/ or class namespace in a theme or plugin, which is very `_doing_it_wrong`.

If a client wants to check that your API exists on a site, they can check against this list. (For more information, see the [Discovery guide](/guide/discovery/).)

$param = $request['some_param'];

$param = $request->get_param( 'some_param' );

$parameters = $request->get_params();

$parameters = $request->get_url_params();

$parameters = $request->get_file_params();

This callback can be registered as `permission_callback`, again in the endpoint options next to your `callback` option. This callback should return a boolean or a `WP_Error` instance. If this function returns true, the response will be proccessed. If it returns false, a default error message will be returned and the request will not proceed with processing. If it returns a `WP_Error`, that error will be returned to the client.

$data = array();

$params = $request->get_params();

$data = $this->prepare_item_for_response( $item, $request );

if ( 1 == 1 ) {

}else{

return current_user_can( 'edit_something' );

When a custom post type or custom taxonomy has been added by code that you do not control, for example a theme or plugin you are using, you may need to add REST API support after it has alredy been registered. The arguments are the same as in the previous examples, but need to be added to the global `$wp_post_types` and `$wp_taxonomies` arrays.

The above example covers a lot. The important part to note is that in the second route we register, we add on a path variable `/(?P[\d]+)` to our resource path `/products`. The path variable is a regular expression. In this case it uses `[\d]+` to signify that should be any numerical character at least once. If you are using numeric IDs for your resources, then this is a great example of how to use a path variable. When using path variables, we now have to be careful around what can be matched as it is user input.

Responses are the data you get back from the API. The `WP_REST_Response` provides a way to interact with the response data returned by endpoints. Responses can return the desired data, and they can also be used to return errors.

if ( isset( $request['params'] ) && ! is_array( $request['params'] ) ) {

There's also a <a href="https://github.com/WP-API/Basic-Auth">Basic Authentication</a> plugin.

* User`

console.log( postCategories[0].name );

console.log( user.get( 'name' ) );

console.log( image );

post.setCategories( [ 'apples', 'oranges' ] );

var appleCategory = allCategories.findWhere( { slug: 'apples' } );

appleCategory.set( 'parent_post', post.get( 'id' ) );

postCategories.create( appleCategory.toJSON(), { type: 'POST' } );

postCategories.at( 0 ).get( 'name' );

to get the last 10 posts:

to get the last 25 posts:

use filter to change the order & orderby options:

to get page 5 of a collection:

check if the collection has any more posts:

console.log( revisions );

If you add custom endpoints to the api they will also become available as models/collections. For example, you will get new models and collections when you [add REST API support to your custom post type](http://v2.wp-api.org/extending/custom-content-types/). Note: because the schema is stored in the user's session cache to avoid re-fetching, you may need to open a new tab to get a new read of the Schema.