Census › Plugin profiles › WooCommerce Legacy REST API
WooCommerce Legacy REST API
Figures from the Plugin Directory Census · as of 28 Aug 2026
400,000
Active installs, lower bound
Group: 100,000 to 999,999 installs
582
Days since the last release
Group median: 12
1.5
out of 5, from 29 ratings
Group median: 4.7 (10+ ratings)
0.0%
Support threads marked resolved, two months
Group: 68.2%
Full profile on wordpress.orgShow on the mapCompare with your own plugins
What is WooCommerce Legacy REST API and who is behind it?
WooCommerce Legacy REST API is a WordPress plugin in the “Shop” field, made by Automattic. It has been listed in the directory since 16 Jan 2024, so for 2 years. Automattic has 24 plugins with at least 10,000 installs in the census. With 400,000 to 499,999 active installs it belongs to the 100,000 to 999,999 installs group; its last release came 582 days before the reference date, and it does not state a tested WordPress version.
This is how the author describes the plugin on wordpress.org:
“The WooCommerce Legacy REST API, which is now part of WooCommerce itself but will be removed in WooCommerce 9.0.”
Self-description on wordpress.org, retrieved on 10 Sept 2026
When was WooCommerce Legacy REST API last released?
The last release of WooCommerce Legacy REST API came 582 days before the reference date; the group median is 12 days. That makes WooCommerce Legacy REST API silent in the census, meaning no release for more than 365 days, as are 5.3% of the group.
How many installs does WooCommerce Legacy REST API have?
WooCommerce Legacy REST API had 400,000 to 499,999 active installs on the reference date. Within its group, 66 plugins had a higher band and 21 plugins the same band.
The API reports installs only as a lower bound with one significant figure: 400,000 means at least 400,000 and at most 499,999.
Which WordPress version is WooCommerce Legacy REST API tested with?
On the reference date the plugin page on wordpress.org showed the notice “This plugin hasn’t been tested with the latest 3 major releases of WordPress”, because the “tested up to” field was below 6.9 (not stated). The notice describes only that field; it does not say whether the plugin runs on newer versions. 8.0% of the group carried it.
How does WooCommerce Legacy REST API compare with its group?
The group holds 399 listed plugins. 97.0% of them had a more recent last release than WooCommerce Legacy REST API; 5.3% had no release for more than 365 days.
| Figure | WooCommerce Legacy REST API | Group, 399 plugins |
|---|---|---|
| Days since the last release | 582 | median 12 |
| Rating | 1.5 (29) | median 4.7 (10+ ratings) |
| Support threads marked resolved | 0.0% | 68.2% |
| Tested up to | not stated | 47.6% on 7.1 |
| Requires PHP | 7.4 | most often 7.4 (41.6%) |
All values on the reference date
| Slug | woocommerce-legacy-rest-api |
|---|---|
| Author | Automattic |
| Active installs | 400,000 to 499,999 |
| Last release | 582 days before the reference date |
| Tested up to | not stated |
| Requires WordPress | 6.2 |
| Requires PHP | 7.4 |
| Rating | 1.5 out of 5 from 29 ratings |
| Support threads, two months | 0 of 1 marked resolved |
| Listed since | 16 Jan 2024 |
| Total downloads | 2,415,994, updates included |
| Tags | rest-api, woo, woocommerce |
Tags
| Tag | Plugins with 10,000+ installs and this tag | Rank by installs | Median days since release |
|---|---|---|---|
| rest-api | 8 | 1 | 196 |
| woo | 8 | 2 | 9 |
| woocommerce | 171 | 5 | 28 |
Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.
Class of 2024
WooCommerce Legacy REST API has been listed since 16 Jan 2024. Of the 48 plugins with 10,000+ installs added in 2024, 95.8% released within the 365 days before the reference date.
Same group, shared tags
Not a recommendation; the same figures for comparison. Alphabetical.
| Plugin | Active installs | Last release | Rating |
|---|---|---|---|
| Admin Columns | 100,000 to 199,999 | 91 days before the reference date | 4.9 (1,651) |
| Advanced Order Export For WooCommerce | 100,000 to 199,999 | 81 days before the reference date | 5.0 (350) |
| Cart Abandonment Recovery for WooCommerce | 300,000 to 399,999 | 3 days before the reference date | 4.8 (612) |
| CartFlows | 200,000 to 299,999 | 4 days before the reference date | 4.8 (504) |
| Discount Rules for WooCommerce | 100,000 to 199,999 | 3 days before the reference date | 4.9 (1,355) |
| FiboSearch | 100,000 to 199,999 | 10 days before the reference date | 4.9 (1,814) |
| Google Analytics for WooCommerce | 100,000 to 199,999 | 3 days before the reference date | 2.8 (119) |
| Google for WooCommerce | 800,000 to 899,999 | 3 days before the reference date | 2.7 (266) |
Do you maintain WooCommerce Legacy REST API?
If you maintain WooCommerce Legacy REST API, you can link to this profile, for example from your readme or your website. Both snippets show this badge:
HTML
<a href="https://hafenstudios.com/en/census/plugins/woocommerce-legacy-rest-api/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="WooCommerce Legacy REST API in the Plugin Directory Census 01/2026" width="220" height="40"></a>
Markdown
[](https://hafenstudios.com/en/census/plugins/woocommerce-legacy-rest-api/)
The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.
A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.
How to cite
hafenstudios (2026): WooCommerce Legacy REST API, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/woocommerce-legacy-rest-api/
Source and status
All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.
Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.
