Caveat From the REST API docs: Changing or removing data from core REST API endpoint responses can break plugins or WordPress core behavior, and should be avoided wherever possible. That said, there’s a rest_post_query filter (well, rest_{$this->post_type}_query) that will let you modify the WP_Query that’s grabbing your posts, so you should be able to add … Read more
Where should I add the code in the sources files of WP? Never, under any circumstances modify WordPress itself, everything will be lost when you update WordPress So instead, create a plugin! A plugin is just a PHP file in the plugins folder with a comment at the top like this: <?php /** * Plugin … Read more
Update your function post_form as function post_form(WP_REST_Request $request) { $data = $request->get_params(); print_r($data); }
URL endpoint with HTML
add_rewrite_endpoint() and Custom Post Type Archive
Removing “category” from URLs then “add_endpoint()” won’t work…
Extending wp JavaScript base class to make a post request to a custom REST endpoint
How to handle Gutenberg wp.data async errors?
Continue execution after WP REST API response
You can do this like this: function get_custom_search_callback($request) { //$parameters = $request->get_params(); $response = urldecode($request->get_param(‘search’)); return rest_ensure_response($response); } add_action(‘rest_api_init’, ‘add_custom_users_api’); function add_custom_users_api(){ register_rest_route(‘namespace/v1’, ‘custom-search/(?P<search>([a-zA-Z]|%20)+)’, array( ‘methods’ => ‘GET’, ‘callback’ => ‘get_custom_search_callback’ ) ); } Note two things: you have to add %20 to the matched character set you have to urldecode() the search variable value … Read more