Plugin Pulse
← Pulse
R

REST API Console

by Ryan McCue · Uncategorized

Also makes 3 other plugins · 10.3K+ installs across the portfolio →

A console for your site's REST API that lives in your WordPress admin.

⚠ Stale⚠ Likely abandoned⚠ Few reviews
How scoring works →
43 Health · D
Maintenance 3/100
Rating quality 68/100
Support 70/100

43 health vs 56 average across 16,376 Uncategorized plugins

High removal-risk signals

63/100

Maintenance and integrity signals that tend to precede a WordPress.org removal. Not an official status, a heads-up to act.

  • Long abandoned. No update in 9+ years — the top precursor to removal once a vulnerability is found.
  • Compatibility drift. Tested only up to WordPress 4.4.34, well behind 6.8.

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.

29 / 100

Under-optimized

Biggest win: Update recency

Update recency 0/100
WP compatibility 5/100
Rating quality 50/100
Listing tuning 68/100

To rank higher: Last updated 3561 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.

Get the full rank-higher report →

Daily downloads

Since 2022-10-05 · 1,426 days · wp.org + Plugin Pulse archive

+47% vs prior 30d
0Downloads · Aug 26

30-day downloads

Rolling 30-day volume · peaks are release surges

56

now · peak 106

5630d downloads · Aug 26

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

REST API Console · #18281 you WooCommerce Legacy R · #144 Disable REST API · #509 Make Connector · #561

Rating trend

Star average over time · dips mark rough releases

2Stars · Aug 26

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.

800per 1k installs · Aug 26

Release cadence

No release in a year
from wp.org release tags

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

0

releases in the last 12 months

9.8y ago

latest release · v2.1

3

tagged releases on record

Recent releases

2.1 · 9.8y ago2.0.1 · 11.0y ago2.0 · 11.1y ago

What its installed base runs

via wordpress.org

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

v2.1 100%

Estimated active installs

The public count shows “70+”. Our estimate pins where the real number sits.

tracked estimate
70–80 ≈77

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

Install history · since 2015-08-13 · 1,384 observations

70Installs · Aug 26

Estimated value

What this plugin might earn a year, and what it might sell for. Modeled from public signals; we don't see anyone's books.

Est. annual revenue

N/A

Est. acquisition value

N/A

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.

Details

Version
2.1
Last updated
9.8y ago
Added
2015-07-15 · 11 yrs old
Requires WP
4.2
Tested up to
4.4.34
Requires PHP

Recent reviews

All reviews on wp.org ↗
  1. Jules Colle
    6.4y ago

    Good start, but this could be a million percent more useful if you simply added the ability to edit the query instead of just appending something. For example: a query like this will never work: /wp/v2/pages/(?P<id>[\d]+) I agree it’s nice to have it as a reference, and it should defenitly stay, BUT when you click on it, you should have an options to edit the query to turn it into /wp/v2/pages/123. I know I could get kind of the same result (except it will be wrapped inside an array) with /wp/v2/pages/?include=123, but meh.. Anyway, I’ll probably modify the plugin and create this myself, as it seems development has ceased.

    Read on wp.org ↗

Behavioral tests

via WP Hive

Automated install-time checks, tested on PHP 7.2.16 · WP 5.3

Low memory footprint
Low page-speed impact
Runs on latest PHP + WP
No PHP errors
No JS errors
Activates cleanly
No resource errors
No external HTTP errors
Optimized database use
Frequently updated

Growth timeline

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

  1. 2026-05-04 80+ → 70+ down after 3 days in tier
  2. 2026-05-01 70+ → 80+ up after 7 days in tier
  3. 2026-04-24 80+ → 70+ down after 266 days in tier
  4. 2025-08-01 90+ → 80+ down after 4 days in tier
  5. 2025-07-28 80+ → 90+ up after 54 days in tier
  6. 2025-06-04 90+ → 80+ down after 74 days in tier
  7. 2025-03-22 100+ → 90+ down after 2 days in tier
  8. 2025-03-20 90+ → 100+ up after 2 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).

Compare head to head →

Embed this report card

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

<iframe src="https://plugins.wpmayor.com/embed/rest-api-console" width="480" height="300" style="border:0" loading="lazy" title="REST API Console — Plugin Pulse"></iframe>
Preview card ↗

REST API Console: 70+ active installs, 2.0★ (1 reviews). Plugin Pulse (WP Mayor), as of 2026-08-31. https://plugins.wpmayor.com/plugin/rest-api-console