REST API Log
by Pete Nelson · Uncategorized
Also makes 7 other plugins · 6.5K+ installs across the portfolio →
WordPress plugin to log REST API requests and responses
Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.
Health
B 81/100
no flags
Active installs
5K+
≈5.5K estimated
Momentum
-22%
downloads vs prior 30d
Biggest opportunity: Swap “json” for “rest”. “json” isn't earning its slot: you're not in the first 24 results for its own search. “rest” sits at #5 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
Install conversion
How it's measured →3.8%
of downloads still active
At least 5K of 131.5K lifetime downloads are still running, above its category: the median Uncategorized plugin keeps 0.6%, across 17,782 plugins.
Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Uncategorized plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.
This plugin shipped 3 releases in the last 12 months, and every existing install that updated counted as another download. wp.org publishes no split between first installs and updates, so we show the raw rate rather than guess at one.
Details
Directory ranking optimization
How it's scored →How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.
Excellent listing optimization
Well tuned across the board
Updated 39 days ago
Tested up to WordPress 7.1.4, the current branch or newer
3.6★ over 24 reviews, weighted for review count to 3.9★ and held back under 25 reviews
5 of 5 tags set · short description in place
Search visibility
How it's tracked →Directory searches this plugin turns up in, and which way each one is moving. WordPress.org publishes no history of search positions, so this starts the day we first tracked a keyword and never backfills.
44
Momentum
Holding steady
+0.1
Velocity
places per keyword, 28d
31%
Breadth
of keywords climbing, 28d
-0.1
Acceleration
recent half vs earlier
wp.org is where the directory puts the plugin for that search. On merit is where it would sit if results were ranked on rating, support and updates, without the install boost. The last column is how far the wp.org position moved, from our first reading in the last 90 days to the latest.
| Keyword | wp.org | On merit | wp.org move, 90 days |
|---|---|---|---|
| elasticsearch your tag | #2 | #2 | 0 |
| elasticpress your tag | #3 | #3 | 0 |
| rest api your tag | #4 | #9 | up 1 |
| rest | #5 | #13 | up 2 |
| json rest api | #3 | #5 | up 2 |
| api rest | #5 | #11 | down 1 |
| api | #16 | #19 | up 1 |
| disable rest api | #6 | #14 | up 1 |
| log | #19 | #22 | up 2 |
| json api | #7 | #13 | up 2 |
| responses | #18 | #21 | up 2 |
| disable json api | #9 | #21 | 0 |
| wp rest api 2 | #10 | #22 | — |
| requests log | #10 | #19 | — |
| wordpress rest api | #11 | #17 | down 1 |
| wp rest api | #11 | #20 | 0 |
| rest api security | #14 | #17 | down 2 |
| no api | #17 | #19 | 0 |
| log in | #20 | #24 | 0 |
| wp rest | #22 | #23 | up 2 |
| json your tag | Not in the top 24 | ||
| logging your tag | Not in the top 24 | ||
57 searches this plugin appeared in over the last 90 days, 20 listed. 37 left out as unrelated or noise (years, numbers, stray words). 2 of its tags aren't in the top 24 for their own search.
What to do about it
- Swap “json” for “rest”. “json” isn't earning its slot: you're not in the first 24 results for its own search. “rest” sits at #5 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.
Daily downloads
Since 5 Oct 2022 · 1,491 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peak 5.3K · peaks are release surges
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
Rating trend
Star average over time · dips mark rough releases
Health trend
Composite health score, snapshotted daily
Update activity
How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.
Release cadence
Occasionally updatedHow often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.
3
releases in the last 12 months
1mo ago
latest release · v1.7.3 · 25 Sep 2026
24
tagged releases on record
Recent releases
What its installed base runs
via wordpress.orgShare 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.
Estimated active installs
The public count shows “5K+”. Our estimate pins where the real number sits.
Crossed into this band 16 months ago; a band this size takes about a year or more to cross, which places it about 50% of the way through.
Install history since 5 Sep 2015
Recent reviews
All reviews on wp.org ↗- ★★★★★ mydigitalsauce12mo 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 ↗ - ★★★★★ floow951.8y 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 ↗ - ★★★★★ blizam3.4y 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 ↗ - ★★★★★ ultrono3.7y 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 ↗ - ★★★★★ con5.3y ago
This is great tool to log REST API calls. Period.
Read on wp.org ↗ - ★★★★★ jnz315.5y 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 ↗ - ★★★★★ Patrik Csak5.8y ago
Thanks!
Read on wp.org ↗ - ★★★★★ amykant6.4y 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 ↗
Latest updates
via wp.org changelogRecent releases and news for this plugin
- — 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
- — 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
- — Version 6.9 Updated highlight.js version Updated clipboard.js version 6.9
- — 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
- — 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
- — 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
Security history
via Wordfence IntelligenceAll 3 disclosed vulnerabilities are patched in the current version (1.7.3). Sites still on an older version should update.
- 2026-10-01 CVE-2026-100514 Authorization Bypass Through User-Controlled Key Affects <= 1.7.2 Patched in 1.7.3
- 2026-08-07 CVE-2026-66443 Exposure of Sensitive Information to an Unauthorized Actor Affects <= 1.7.1 Patched in 1.7.2
Vulnerability records provided by Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. License and terms.
CVE records: Copyright 1999-2026 The MITRE Corporation. CVE terms of use.
Languages
via translate.wordpress.orgTranslated into 135 languages, 3 at 90% or more
Plus 111 more locales with partial translations.
AI assistants
How it's measured →Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.
This plugin’s searches fall outside the topics measured so far. See the topics measured so far.
Readme readiness
2 of 8 pass · checked 2 Nov 2026Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.
- ! Says what it does Short description names no action; say what the plugin does for the site.
- ! Has a FAQ Only 1 question in the FAQ; 3 or more gives an assistant something to match.
- ! FAQ asks real questions 0 of 1 FAQ entries are headings, not questions ("undefined").
- ! Names who it is for Never says who the plugin is for or what they use it for.
- ✓ Names what it works with Mentions REST API.
- ! Headings and lists 0 headings and 2 lists; assistants quote headed sections and bullet lists, not paragraphs.
- ! Enough to quote 353 characters of description; under 1,000 there is little to quote.
- ✓ Tags match the text 4 of 5 tags appear in the text; "elasticsearch" does not.
Growth timeline
Install-tier crossings we have observed, and how long each tier took to outgrow
- 2025-07-26 6K+ → 5K+ down after 50 days in tier
- 2025-06-06 5K+ → 6K+ up after 941 days in tier
- 2022-11-08 4K+ → 5K+ up after 407 days in tier
- 2021-09-27 3K+ → 4K+ up after 144 days in tier
- 2021-05-06 2K+ → 3K+ up after 481 days in tier
- 2020-01-11 1K+ → 2K+ up after 709 days in tier
- 2018-02-01 700+ → 1K+ up after 215 days in tier
- 2017-07-01 500+ → 700+ up after 90 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 7K+ installs · 3.8★ · 2 shared tags D - W WP REST API Meta Endpoints 1K+ installs · 3.6★ · 2 shared tags
-
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.
<iframe src="https://plugins.wpmayor.com/embed/wp-rest-api-log" width="480" height="300" style="border:0" loading="lazy" title="REST API Log — Plugin Pulse"></iframe> REST API Log: 5K+ active installs, 3.6★ (24 reviews). Plugin Pulse (WP Mayor), as of 2026-11-03. https://plugins.wpmayor.com/plugin/wp-rest-api-log
Spotted a number that looks wrong? Report a data issue and we'll check it against the source.