So getEntityRecords( ‘taxonomy’, ‘genre’ ) will make a request to the “list terms” endpoint at /wp/v2/genre (or /wp/v2/<rest_base> if your taxonomy uses a custom rest_base) in the REST API, and because the “list terms” endpoint for custom taxonomies by default use the same parameters used by /wp/v2/categories (the “list terms” endpoint for the built-in category … Read more
You don’t need to include query parameters in the endpoint. Just the path: register_rest_route( ‘myplugin/v1’, ‘/posts’, array( ‘methods’ => ‘GET’, ‘callback’ => ‘my_rest_function’, ‘permission_callback’ => ‘__return_true’, ‘args’ => array( ‘number’ => array( ‘validate_callback’ => function( $param, $request, $key ) { return is_numeric( $param ); } ), ‘offset’ => array( ‘validate_callback’ => function( $param, $request, $key … Read more
The routes in question have two or three default endpoints: /wp/v2/users — it has two endpoints, one GET and one POST, i.e. “List Users” (GET /wp/v2/users), and “Create a User” (POST /wp/v2/users). /wp/v2/users/<id> — it has three endpoints, one GET, one POST and one DELETE, i.e. “Retrieve a User” (GET /wp/v2/users/<id>), “Update a User” (POST … Read more
You could hook into the login process in the WP site and create a unique token (stored in meta) for that user on login. The token can then be sent to the other server, that could query the WP API with that token. You would have to create a custom endpoint that validates the user … Read more
WP REST API depends on WordPress, as it is just another interface for interacting with its other APIs. If BackPress (https://backpress.org/) was still in development, you could have had some chance with it, but it seems the project is abandoned. The plugin that was merged with WordPress Core is available here: https://github.com/WP-API/WP-API but is also … Read more
I solved the issue thanks to this answer: Serialized settings in rest api. I was able to store all the options as a json object: /** * Create plugin options schema as an object and prepare it for the rest api. * WP >=5.3 */ function my_register_settings() { $general_options = [ ‘show_in_rest’ => [ ‘schema’ … Read more
The problem may be pagination The API only returns 10 results per page, and needs follow up requests to fetch the rest. WP includes a HTTP header that tells you how many total results and the number of pages. It has a hard limit of 100 per page maximum, if you request 200, you will … Read more
Ok. I found this on StackOverflow: &_fields[]=title&_fields[]=_links. (Or just &_fields[]=link). It works. I guess it would work for any of the fields in the complete return package though I haven’t tested it.
In general I would be careful modifying existing endpoints, but you could try using the object passed into the callback, e.g.: ‘get_callback’ => function( $object ) { return date_i18n( __( ‘j. F Y, H:i’, ‘wpse’ ), strtotime( $object[‘date’] ) ); },
Out of the box there is no mechanism for a user to login via the REST API to begin a session without pre-configured access. WordPress Core provides 2 authentication methods for the REST API: cookies + nonces application passwords Likewise there is no mechanism for registering for an account via the REST API, user creation … Read more