It’s because of how you’ve defined the accepted methods: ‘methods’ => ‘\WP_REST_Server::CREATABLE ‘, You shouldn’t have quotes around it. WP_REST_Server::CREATABLE is a string that equals ‘POST’, but by putting quotes around it you’re literally setting the method as ‘\WP_REST_Server::CREATABLE’, which is not a valid HTTP method. You can see this in the response to the … Read more
According to http://v2.wp-api.org/reference/posts/ you have categories_exclude available as a param to pass to the API. This should work: http://localhost/wp-json/wp/v2/events/?categories=23&categories_exclude=42&per_page=1 …to get the posts from category 23, but exclude those that also have 42 assigned as category.
According to ticket #38373 the following endpoints will be supported in version 4.7. Let me quote Rachel Baker: REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of … Read more
Could this be about https://core.trac.wordpress.org/ticket/39432 Symptoms look very similar and at the time of writing hasn’t been released as 4.7.3. Applying the patch manually fixed the issue on my nginx setup.
As of WordPress 4.7 now we have the following filter to hook to: $args = apply_filters( “rest_{$this->post_type}_query”, $args, $request ); So if you would like to perform a request like: http://yoursite.com/wp-json/wp/v2/posts?meta_key=your_key&meta_value=your_value&per_page=10 OR http://yoursite.com/wp-json/wp/v2/posts?meta_query[0][key]=your_key&meta_query[0][value]=your_value&per_page=10 you can do it through the following piece of code (within your functions.php): /** * This function will allow custom parameters within … Read more
Authorization header is usually stripped by Apache. You can fix it with .htaccess RewriteEngine On RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule .* – [e=HTTP_AUTHORIZATION:%1]
Here’s a REST API recipe for latest post per site on a multi-site, for relatively few sites: Use get_sites(), loop over sites and switch to each site, query latest post on each site, collect data, order data by utime, serve data Example REST Routes https://example.com/wp-json/wpse/v1/latest-post-per-site https://example.com/wp-json/wpse/v1/latest-post-per-site?number=10 https://example.com/wp-json/wpse/v1/latest-post-per-site?debug Example Plugin Here’s a demo plugin implementing the … Read more
Say you start with a server that is completely empty. You haven’t installed WordPress yet. Now if you visit those wp-json URLs, your server goes and looks for corresponding directories / files that match your request, and of course it is empty, so as you would expect, you get 404 errors. Now install default WordPress, … Read more
‘Authenticate’: ‘Basic {what do I put here?}’ // Do I need “Basic”? No, it’s not Basic. It’s Bearer. And the header is Authorization. So first, obtain a token from /wp-json/jwt-auth/v1/token: fetch( ‘http://example.com/wp-json/jwt-auth/v1/token’, { method: ‘POST’, body: JSON.stringify( { // Username of a user on the WordPress website in which the REST API request // is … Read more
If you have access to your request header you can add the line. Cache-Control: private or Cache-Control: no-cache. This will force well-behaved hosts to send you fresh results.