Title: Headless REST API Security Author: Md. Rakib Ullah Published: 2026-01-20 Last modified: 2026-02-22 --- Szukaj wtyczek ![](https://ps.w.org/headless-rest-api-security/assets/banner-772x250.png?rev=3443475) ![](https://ps.w.org/headless-rest-api-security/assets/icon-256x256.png?rev=3443475) # Headless REST API Security Autor: [Md. Rakib Ullah](https://profiles.wordpress.org/rakib417/) [Pobierz](https://downloads.wordpress.org/plugin/headless-rest-api-security.2.3.zip) * [Szczegóły](https://pl.wordpress.org/plugins/headless-rest-api-security/#description) * [Recenzje](https://pl.wordpress.org/plugins/headless-rest-api-security/#reviews) * [Instalacja](https://pl.wordpress.org/plugins/headless-rest-api-security/#installation) * [Rozwój](https://pl.wordpress.org/plugins/headless-rest-api-security/#developers) [Wsparcie](https://wordpress.org/support/plugin/headless-rest-api-security/) ## Opis 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-KEY` header 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 1. Navigate to **Settings > Headless Security** in the WordPress dashboard. 2. Enable the **Master Switch** to activate the access restrictions. 3. Review the list of REST API routes and check the **Allow** box for endpoints the application requires. 4. Copy the generated **API Key** for use in application headers. 5. (Optional) Enter a **Headless Frontend URL** to configure redirects for visitors. ## Zrzuty ekranu * [[ * **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. ## Instalacja 1. Upload the plugin files to the `/wp-content/plugins/headless-rest-api-security` directory, or install the plugin through the WordPress plugins screen. 2. Activate the plugin through the 'Plugins’ screen in WordPress. 3. Go to the **Headless Security** menu to configure allowed routes. ## Najczęściej zadawane pytania ### Does this modify WordPress Core files? No. The plugin uses standard WordPress hooks (`rest_authentication_errors` and ` template_redirect`) to manage access. ### Will this affect the Block Editor (Gutenberg)? The plugin checks for logged-in users with the `edit_posts` capability, 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 ## Recenzje ![](https://secure.gravatar.com/avatar/7c3aa29708077177e413cb6a017a52eb7cc621f92a76d30baff0de2402572e8c? s=60&d=retro&r=g) ### 󠀁[Best Plugin for Securing Headless WordPress](https://wordpress.org/support/topic/best-plugin-for-securing-headless-wordpress/)󠁿 [Ridhwan Ahsan](https://profiles.wordpress.org/ridhwanahsann/) 2026-02-16 1 odpowiedź Excellent plugin! Secures my headless WordPress API quickly and easily. Works perfectly with Next.js and mobile apps ![](https://secure.gravatar.com/avatar/4b21d167926badc780294bc91dc19bddc3ad39e36a1c0423df9c7f39c29b335b? s=60&d=retro&r=g) ### 󠀁[Easy to use and secure](https://wordpress.org/support/topic/easy-to-use-and-secure/)󠁿 [Ashikjs](https://profiles.wordpress.org/mostofa55688/) 2026-02-04 1 odpowiedź Great plugin. Simple setup, easy to use, and it effectively secures my site’s REST API. Highly recommend. [ Przeczytaj 1 recenzje ](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/) ## Kontrybutorzy i deweloperzy „Headless REST API Security” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki. Zaangażowani * [ Md. Rakib Ullah ](https://profiles.wordpress.org/rakib417/) [Przetłumacz wtyczkę “Headless REST API Security” na swój język.](https://translate.wordpress.org/projects/wp-plugins/headless-rest-api-security) ### Interesuje cię rozwój wtyczki? [Przeglądaj kod](https://plugins.trac.wordpress.org/browser/headless-rest-api-security/), sprawdź [repozytorium SVN](https://plugins.svn.wordpress.org/headless-rest-api-security/) lub czytaj [dziennik rozwoju](https://plugins.trac.wordpress.org/log/headless-rest-api-security/) przez [RSS](https://plugins.trac.wordpress.org/log/headless-rest-api-security/?limit=100&mode=stop_on_copy&format=rss). ## Rejestr zmian #### 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. ## Meta * Wersja **2.2** * Ostatnia aktualizacja **3 miesiące temu** * Włączone instalacje **20+** * Wersja WordPressa ** 5.8 lub nowszej ** * Testowano do **6.9.4** * Wersja PHP ** 7.4 lub nowszej ** * Język * [English (US)](https://wordpress.org/plugins/headless-rest-api-security/) * Tagi * [access-control](https://pl.wordpress.org/plugins/tags/access-control/)[authentication](https://pl.wordpress.org/plugins/tags/authentication/) [headless](https://pl.wordpress.org/plugins/tags/headless/)[permissions](https://pl.wordpress.org/plugins/tags/permissions/) [rest-api](https://pl.wordpress.org/plugins/tags/rest-api/) * [Widok zaawansowany](https://pl.wordpress.org/plugins/headless-rest-api-security/advanced/) ## Oceny 5 na 5 gwiazdek. * [ 2 recenzje 5-gwiazdkowe ](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/?filter=5) * [ 0 recenzji 4-gwiazdkowych ](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/?filter=4) * [ 0 recenzji 3-gwiazdkowych ](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/?filter=3) * [ 0 recenzji 2-gwiazdkowych ](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/?filter=2) * [ 0 recenzji 1-gwiazdkowych ](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/#new-post) [Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/headless-rest-api-security/reviews/) ## Zaangażowani * [ Md. Rakib Ullah ](https://profiles.wordpress.org/rakib417/) ## Wsparcie Masz coś do dodania? Potrzebujesz pomocy? [Zobacz forum wsparcia](https://wordpress.org/support/plugin/headless-rest-api-security/)