Description
Running a Headless WordPress site often involves exposing the REST API. Headless REST API Security provides tools for administrators to control which endpoints are accessible to the public or external applications.
This plugin restricts public access to REST API endpoints by default and offers a settings interface to allow-list only the specific routes required by a frontend application (such as Next.js, Gatsby, or mobile apps).
Features
- Access Control: Restrict default public access to REST API endpoints.
- Route Allow-Listing: Specific API routes (e.g.,
/wp/v2/posts) can be enabled while others remain restricted. - API Key Authentication: Supports an
X-API-KEYheader for server-to-server or frontend requests. - Headless Redirect: Option to redirect users accessing the backend API URL to a specified frontend domain.
- Admin Access: Logged-in Administrators and Editors retain access to the API to support the Block Editor (Gutenberg) functionality.
- Plugin Support: Detects routes registered by third-party plugins for configuration.
Usage
- Navigate to Settings > Headless Security in the WordPress dashboard.
- Enable the Master Switch to activate the access restrictions.
- Review the list of REST API routes and check the Allow box for endpoints the application requires.
- Copy the generated API Key for use in application headers.
- (Optional) Enter a Headless Frontend URL to configure redirects for visitors.
Screenshots
General Settings: The main configuration screen with the Master Switch and Redirect URL options. 
Route Manager: The grid view for allowing or restricting specific API namespaces and endpoints.
Installation
- Upload the plugin files to the
/wp-content/plugins/headless-rest-api-securitydirectory, or install the plugin through the WordPress plugins screen. - Activate the plugin through the ‘Plugins’ screen in WordPress.
- Go to the Headless Security menu to configure allowed routes.
FAQ
-
Does this modify WordPress Core files?
-
No. The plugin uses standard WordPress hooks (
rest_authentication_errorsandtemplate_redirect) to manage access. -
Will this affect the Block Editor (Gutenberg)?
-
The plugin checks for logged-in users with the
edit_postscapability, allowing the backend editor to function normally while restrictions are active. -
Can I use this with custom endpoints?
-
Yes. Registered REST API routes appear in the settings list and can be allow-listed.
-
Where is the API Key placed?
-
The key is sent in the request header. Example:
X-API-KEY: your_generated_key_here
Reviews
Contributors & Developers
“Headless REST API Security” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Headless REST API Security” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
2.3
- Fix: Resolved a critical error on the settings page caused by third-party plugin conflicts with REST API initialization.
- Fix: Resolved stable tag and version mismatch issues for WordPress.org compliance.
2.2
- Updated UI styles for better accessibility.
- Improved checkbox contrast.
2.1
- Minor code improvements.
2.0
- Added route allow-listing functionality.
- Added headless frontend redirect feature.
- Added admin bypass for authenticated users.
1.0
- Initial release.