Getting user names and passwords is a horrible idea I hope no user will actually agree to, but beyond that your idea to do it from JS is going to fail due to CORS, which means you will have to do it in AJAX to your server, and let your server try to login, which … Read more
Pretty much all the URLs you are using are invalid in some way: http://foobar.com/wp-json/wp/v2/posts/categories_name=hello categories_name is not a valid argument for listing posts, and even if it was you are missing the ? part of the query string. http://foobar.com/wp-json/wp/v2/posts/categories_name=hello?per_page=1 This one is also missing the ?. Query parameters on a URL, which the API uses … Read more
GET requests, like listing posts, doesn’t need authentication at least you need to get private posts. Your problem is that you are using a route/endpoint that doesn’t exist. In WordPress 4.4, WP REST API infrastructure was merged, endpoints didn’t; they will be merged in WordPress 4.5 (as WordPress 4.6 it seems endpoints are still don’t … Read more
You can actually find extensive documentation on wordpress.org. But let’s have a look at this particular example: https://demo.wp-api.org/wp-json/wp/v2/posts?per_page=5&tags=3 The 5 in there is the number of posts you want returned. The 3 is the id of the tag you want to limit the posts too. If you want to limit to a category use categories … Read more
Make sure your post type is shown in the REST API. $args = array( //* Use whatever other args you want ‘show_in_rest’ => true, ‘rest_base’ => ‘myslug’, ‘rest_controller_class’ => ‘WP_REST_Posts_Controller’, ); register_post_type( ‘myslug’, $args ); The endpoint to create a post would then be http://example.com/wp-json/wp/v2/myslug. Edit: The above is all that’s needed for a custom … Read more
To add the user’s email address in the REST API response, register an additional field to the user object and add the email address: register_rest_field( ‘user’, ‘user_email’, [ ‘get_callback’ => static function (array $user): string { return get_userdata($user[‘id’])->user_email; }, ] ); Please note, however, that this is strongly discouraged because anyone can then see the … Read more
After some inspecting the WP_REST_Request, it turned out, that the get_body() method was the one I’m looking for. Anyhow, this is what I ended up with: add_action( ‘rest_api_init’, function() { register_rest_route( ‘ep’, ‘/as/’, [ ‘methods’ => \WP_REST_Server::CREATABLE, ‘callback’ => ‘ep_autosuggest’, ] ); } ); function ep_autosuggest( WP_REST_Request $data ) { // Elasticsearch PHP Client $client … Read more
This is totally possible by registering your own rest field into the response. Here’s some documentation on modifying response data. https://developer.wordpress.org/rest-api/extending-the-rest-api/modifying-responses/ Here’s how to add roles to the endpoint: function get_user_roles($object, $field_name, $request) { return get_userdata($object[‘id’])->roles; } add_action(‘rest_api_init’, function() { register_rest_field(‘user’, ‘roles’, array( ‘get_callback’ => ‘get_user_roles’, ‘update_callback’ => null, ‘schema’ => array( ‘type’ => ‘array’ … Read more
First off.. (This info is for other readers who don’t know yet about this.) There are two ways of how you can authenticate your REST API request: Using the standard cookie authentication Using a plugin like Application Passwords You can read more on the official REST API Handbook here, and this answer is for the … Read more
No Result found(404) because your plugins endpoints may not have been compatible with the WP Rest API v2. Please see the list if they are compatible or not : http://v2.wp-api.org/guide/plugins/