| 开发者 | martincipriano |
|---|---|
| 更新时间 | 2026年5月25日 11:49 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/wpbuoy-endpoint-manager directory, or install the plugin through the WordPress plugins screen directly.Disabling certain endpoints may affect WordPress functionality, plugins, or themes that depend on the REST API. Always test thoroughly after making changes. We recommend testing on a staging site first.
Blocked endpoints return a 403 Forbidden response. The endpoint remains registered in WordPress — it's not removed, just inaccessible. You can re-enable it at any time from the admin screen.
The Block Editor relies on several /wp/v2/ REST API routes. Review those endpoints carefully and test on a staging site before disabling any of them.
Yes. The plugin shows all registered static REST API endpoints, including those from plugins and themes.
Yes, but the plugin must be activated on each site individually. Network activation is not currently supported.
No. The plugin adds a minimal check at the REST API permission layer. There is no impact on front-end performance.
Yes. All toggles are reversible — just re-enable any endpoint from the admin screen. If you uninstall the plugin, all settings are removed automatically.
No. Viewing, searching, filtering, previewing endpoints, and reviewing security logs are all available for free. Endpoint blocking and Pro features require an active license.