If the API is expecting a JSON object you should change your args to: $args = array ( ‘sslverify’ => false, ‘data_format’ => ‘body’, ‘headers’ => [ ‘Authorization: Bearer {API_KEY}’, ‘Content-Type: application/json’ ], ‘body’ => json_encode([ ‘region’ => ‘USA’, ‘plan’ => 1, ‘label’ => ‘API Test’, ‘app_id’ => 2 ]), ); Encode your data into … Read more
You can “block” them, by simply removing their existence from the REST Server. WP provides a filter for the REST API endpoints, you simply have to filter this with your routes. The below is a simple PHP Class that does this for you. All you need to do is provide the array of routes. I’ve … Read more
I solved following this answer and writing: public function query_wasb_messages_by_status( $args, $request ) { if ( ! is_null( $request->get_param( ‘message_status’ ) ) ) { $args[‘meta_query’] = array( ‘_wasb_message_status’ => array( ‘key’ => ‘_wasb_message_status’, ‘value’ => (int) $request->get_param( ‘message_status’ ), ‘compare’ => ‘=’, ‘type’ => ‘numeric’ ) ); } return $args; } add_filter( ‘rest_wasb_message_query’, array( $this, … Read more
I think the most simple solution would be to use a custom filter for this. It could look something like: $schema = apply_filters(‘pluginA/register/country’, [ “type” => “string”, “description” => “The user’s country”, “arg_options” => [ “sanitize_callback” => function( $value ) { return sanitize_text_field( $value ); }, “validate_callback” => function( $value ) { return is_string( $value … Read more
Watch your keys: $headers = array( // ‘headers’ => array( // this is duplicated ‘Authorization’ => ‘Basic ‘ . base64_encode( ‘username:password’ ), ‘Accept’ => ‘application/xml’ // ) ); $res = wp_remote_request( $url, array( ‘method’ => ‘GET’, ‘headers’ => $headers ) ); Don’t send headers inside headers. Using a variable name different from args can help … Read more
In order to accomplish this, I created a custom data store and extracted the available meta keys from the routes object returned when hitting the wp-json/wp/v2/ endpoint in the editor. This approach decreased the number of API requests compared to that with which I started. The initial approach in the question would have made one … Read more
This may not be the best answer but for the time being, I’ve been able to get what I want through querying again via a WP_REST_Request using the results I’ve got from the WP_Query mentioned earlier. So the full solution looks like this. function get_blog_posts() { $posts = new WP_Query( array( ‘post_type’ => ‘post’, ‘posts_per_page’ … Read more
If you’re pulling REST API data from a WordPress site (“server”) to a non-WordPress site (“client”), your client site won’t have access to WordPress functions like get_the_title(), etc. What you will receive from the server is a JSON string that will look something like this: // eg. from example.com/wp-json/wp/v2/posts [ { “id”:10887, “date”:”2022-05-04T11:25:43″, “date_gmt”:”2022-05-04T16:25:43″, “guid”: … Read more
This is because when your block was rendered for save the API call had not finished. Save components do not run on the frontend. render() { return( <div> Test {this.state.data.length > 0 ? this.state.data.map(data => <div>{data.id}</div>) : ’empty’} </div> ) } The purpose of a save component is to take your blocks attributes, and turn … Read more
So, why the default namespace persist if I did all right? Would it be some javascript function of wordpress that would be doing the request on the incorrect route? What function? How to fix it? If the endpoint works then you changed it correctly, but if you’ve flushed rewrite rules/permalinks, and it still isn’t working, … Read more