REST API Log

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 88% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Refined from the date this plugin crossed into its current band.

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from. A declining trend compresses what a buyer would pay.

1. ★★★★★ mydigitalsauce

   9mo ago

   It will absolutely wreck your database efficiency, it is adding records incorretly to posts and postmeta. It should of registered its own tables, i regret installing.

   Read on wp.org ↗
2. ★★★★★ floow95

   1.6y ago

   The plugin is oding it’s job and for that I am very thankful. A little side note is that it is adding for each log entry a post type to WordPress. On 200.000 API calls per week it has brough our order numbers from #600000 to #900000 within 10 days. Therefore leaving it enabled may not be so recommended. I have disabled it again now. Don’t know if this is solveable but just thought it would be a nice side note.

   Read on wp.org ↗
3. ★★★★★ blizam

   3.2y ago

   The clowns leaving this a 1 star obviously don’t know what it’s intended for… Yes… do NOT leave this plugin running constantly unless you know what you’re doing and understand your particular WP environment and it’s day to day API activity. More plugins than ever use the REST API to interact with WP and your database will increase in size exponential to it’s activity. For most people this tool is intended to help troubleshoot specific API activities and is something that you only turn on for a short period of time while you’re testing/monitoring specific API calls and responses…. and for that, it works beautifully. Thank you!!

   Read on wp.org ↗
4. ★★★★★ ultrono

   3.5y ago

   This extension will make your database huge, so be aware of this if using in production. I’d recommend turning it on for a short period then disabling. Filtering by request method (POST, GET etc.) does not work. Deleting data (at /options-general.php?page=wp-rest-api-log-settings) takes an absolute age, I’m tempted to do this manually in the database. I have ~105,000 log entries. I wish to delete these. According to the API responses, ~100 logs are being deleted every minute. I’m making direct POST requests to the WordPress API (using Postman) and the request method displayed in the log is always GET.The source IP is not always recorded – have tried the IP / X forwarded for option to resolve the IP too. This topic was modified 3 years, 5 months ago by ultrono.

   Read on wp.org ↗
5. ★★★★★ con

   5.2y ago

   This is great tool to log REST API calls. Period.

   Read on wp.org ↗
6. ★★★★★ jnz31

   5.3y ago

   its trash. whilst i do like the idea of the plugin, this tool is simply not working properly. guess it’s abandoned. there is a filter build in to filter for the request type, but it does not work (simply doesn’t filter at all). and there is an option, to purge logs, that are older than x days, but this doesn’t work ether. and deleting the logs takes ages, you might want to do that in the db directly. so handle with care, as it will bloat the db and it’ll be hard to find the data, you might be looking for.. This topic was modified 5 years, 2 months ago by jnz31. This topic was modified 5 years, 2 months ago by jnz31. This topic was modified 5 years, 2 months ago by jnz31.

   Read on wp.org ↗
7. ★★★★★ Patrik Csak

   5.6y ago

   Thanks!

   Read on wp.org ↗
8. ★★★★★ amykant

   6.2y ago

   This was a legacy plugin for a client’s website… I would not recommend it! It bloated our disk usage and one of the tables ended up with 22 million rows. Here are the queries we used to clean things up. -- Run first delete m from wp_posts p join wp_postmeta m on p.ID = m.post_id where post_type = 'wp-rest-api-log' -- Run second delete from wp_posts where post_type = 'wp-rest-api-log' -- Run third DELETE wp_term_relationships FROM wp_term_relationships LEFT JOIN wp_posts ON wp_term_relationships.object_id = wp_posts.ID WHERE wp_posts.ID is NULL;

   Read on wp.org ↗

Recent releases and news for this plugin

1. — Version 7.1 Added additional security check to REST download endpoint (props alisalive) Fixed PHP 8 deprecation notice for submenu page (props BrianHenryIE) Fixed echo bug when viewing an invalid log entry ID (props DAnn2012) 7.1
2. — Version 7.0 Fixed bugs related to Method and Status filtering. Removed deprecated FILTER_SANITIZE_STRING calls. Updated highlight.js version Updated clipboard.js version 7.0
3. — Version 6.9 Updated highlight.js version Updated clipboard.js version 6.9
4. — Version 6.8 Updated the Purge All Entries functionality in the admin to purge batches of 25 at a time. Updated CLI purge command with a progress bar. Fixed ClipboardJS error (props itowhid06) 6.8
5. — Version 6.7 Added admin notice about running the plugin on a production server Set the default purge days to 7 Updated clipboard.js version 6.7
6. — Version 6.6 Moved taxonomy registration to a separate file, made taxonomies not public to prevent them from automatically showing in Yoast SEO sitemaps Updated highlight.js version Updated minimum WP version to 4.7 Updated unit test 6.6

2 disclosed vulnerabilities on record for this plugin, all fixed in the current version. Sites on older versions stay exposed until they update.

1. Medium · 5.3 REST API Log <= 1.7.1 - Unauthenticated Information Exposure ↗
   2026-08-07 CVE-2026-66443 Exposure of Sensitive Information to an Unauthorized Actor Affects <= 1.7.1 Patched in 1.7.2
2. Medium · 5.3 REST API Log <= 1.7.0 - Missing Authorization to Unauthenticated Sensitive Log Data Disclosure ↗
   2026-07-27 CVE-2026-16547 Missing Authorization Affects <= 1.7.0 Patched in 1.7.1

Automated install-time checks, tested on PHP 8.1.12 · WP 6.2

Translated into 135 languages, 3 at 90% or more

Plus 111 more locales with partial translations.

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2025-07-26 6K+ → 5K+ down after 50 days in tier
2. 2025-06-06 5K+ → 6K+ up after 941 days in tier
3. 2022-11-08 4K+ → 5K+ up after 1 days in tier
4. 2022-11-07 5K+ → 4K+ down after 6 days in tier
5. 2022-11-01 4K+ → 5K+ up after 5 days in tier
6. 2022-10-27 5K+ → 4K+ down after 1 days in tier
7. 2022-10-26 4K+ → 5K+ up after 5 days in tier
8. 2022-10-21 5K+ → 4K+ down after 1 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

• Disable REST API 80K+ installs · 4.6★ · 2 shared tags D
• Disable WP REST API 30K+ installs · 4.6★ · 2 shared tags A
• WordPress REST API (Version 2) 10K+ installs · 4.1★ · 2 shared tags D
• WP REST API – OAuth 1.0a Server 8K+ installs · 3.8★ · 2 shared tags D
• W WP REST API Meta Endpoints 1K+ installs · 3.6★ · 2 shared tags D
• ElasticPress Debugging Add-On 800+ installs · 4.1★ · 2 shared tags B

Embed this report card

Drop a live Pulse card for REST API Log into a readme, a review or a deck. It updates itself.

REST API Log: 5K+ active installs, 3.6★ (24 reviews). Plugin Pulse (WP Mayor), as of 2026-08-29. https://plugins.wpmayor.com/plugin/wp-rest-api-log