REST API Log
View on WordPress.orgScores higher than 39% of indexed plugins
About
WordPress plugin to log REST API requests and responses
Security History
What It Does
REST API Log captures incoming and outgoing WordPress REST API requests and responses, storing them in the database so developers can review traffic patterns, debug failed calls, and audit what data is leaving the site. It exposes a dedicated log viewer inside the wp-admin area and supports filtering by endpoint, method, status code, and date range. Essentially, it turns the normally invisible REST traffic on your site into something you can search and replay.
Who It's For
This plugin fits developers and technical teams running headless WordPress setups, WooCommerce stores connected to mobile apps, or any site that uses the REST API as a backend for third-party integrations. It is most useful on staging or production environments where you need to diagnose why an API consumer is getting unexpected responses. Agencies and freelancers debugging client integrations will also find value here.
Who Should Skip It
If you only use WordPress as a traditional CMS without custom API consumers, or if you are not comfortable inspecting raw JSON payloads and HTTP traffic, this plugin adds database overhead without any real benefit. Site owners relying on basic page builders and off-the-shelf themes should skip it entirely.
The Bottom Line
REST API Log is a focused, narrowly useful developer tool that does one thing and does it reasonably well, with a solid last-update date and clean WordPress 6.7.5 compatibility. Its overall quality score of 50.17 reflects a small user base, sparse support history, and no declared PHP requirement, which together drag down an otherwise functional plugin. Use it if you actively debug REST traffic on a regular basis; otherwise, the alternatives will serve you better.
Related Plugins
Pick this instead if your real need is bulk exporting URLs or post data rather than monitoring REST traffic in real time.
Pick this instead if you are building a headless site on GraphQL rather than REST and need a proper query layer, not just logging.
Pick this instead if your main REST API problem is authentication and securing endpoints, not observing what flows through them.
Pick this instead if you want to shut the REST API down entirely for security reasons, rather than log and monitor it.
Pick this instead if your integration headaches are around transactional email delivery rather than REST request inspection.