add_filter('rest_api_init', 'rest_only_for_authorized_users', 99);
function rest_only_for_authorized_users($wp_rest_server)
{
if (!is_user_logged_in()) {
wp_die('REST API is blocked', 'Access denied', 403);
}
}Share this:
Share this article
Related articles
Implementing Google Fonts in React Native App
Want to make your React Native apps look nice and user-friendly? Google Fonts is your best buddy! This…
Building a React Native App with Cached API Calls
Learn how to improve your app's performance and reduce server load by caching API calls in your React…
Setup CI-CD Pipeline in AWS
Executive Summary: Manual builds and deploys slow releases and invite configuration mistakes. This post walks AWS CI/CD setup…
Shared the REST lockdown notes with WP retainer clients. Default-open interfaces feel reckless now.
Hardening endpoints without breaking the block editor needed your exceptions list. Careful reading paid off.
Who may hit /wp-json sat unanswered too long. Allowlist approach from this post is what we implemented.
REST route lockdown landed on our hardening list after a noisy bot week. Access rules here are the starting template.