docs
docs copied to clipboard
The content for developer.wordpress.org/rest-api
On the [schema documentation page](https://developer.wordpress.org/rest-api/extending-the-rest-api/schema/) page, the document links to https://spacetelescope.github.io/understanding-json-schema/index.html for the easier to understand schema. That link is no longer valid. It redirects to https://json-schema.org/understanding-json-schema/index.html which is also...
Added a clarification for required property and empty values being allowed.
Hi, i found out that the following pages dont exist in the left navigation menu (i expected to find them under "Reference" menu) : - https://developer.wordpress.org/rest-api/reference/taxonomies/ - https://developer.wordpress.org/rest-api/reference/users/ - https://developer.wordpress.org/rest-api/reference/post-types/...
Right now it's difficult to find information about working with terms in a custom taxonomy via the REST API. There may be a better place for this, but my hope...
Status value is "active" and not "1". See "class-wp-rest-themes-controller.php" (Ln 91): if ( isset( $registered['status'], $request['status'] ) && in_array( 'active', $request['status'], true ) ) { $active_theme = wp_get_theme(); $active_theme =...
Only 'status=publish' is accepted by now. Other states as draft, future,... return 401 https://example.com/wp-json/wp/v2/posts?status=future It'd be great to get '?status=any' back as well.
Last year at WCEU, @kadamwhite took notes on how a typical REST API request works in WordPress from the top down. We need to get this into some actual form...
The REST v2 `/posts` [endpoint reference](https://developer.wordpress.org/rest-api/reference/posts/) documents its optional `status` argument as letting clients "Limit result set to posts assigned one or more statuses", but does not specify the syntax...
I was researching how to authenticate a WP REST API which access had been restricted by reading the docs here https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/ After a bit more research I stumble upon [this...
In the [The Controller Pattern](https://developer.wordpress.org/rest-api/extending-the-rest-api/adding-custom-endpoints/#the-controller-pattern) section on the Adding Custom Endpoints page, there's an anchor link for [Extending Internal Classes](https://developer.wordpress.org/rest-api/extending-the-rest-api/controller-classes/#extending-internal-classes) that doesn't point to an existing anchor on the target...