Comparison · generated on request
Kill JSON REST API vs WPGet API – Connect to any external REST API
Both plugins as this registry currently observes them. Figures come from the same daily snapshot, so they are directly comparable, which two separate wordpress.org pages, read minutes apart, are not.
| Kill JSON REST API | WPGet API – Connect to any external REST API | |
|---|---|---|
| What it does | Completely disables JSON REST API for both registered and anonymous users in WordPress 4.7.* and removes API links and tags. | Connect any REST API to WordPress. WPGet API enables easy API integration, allowing you to display API data without any code. |
| Active installs | 20+ | 10,000+ |
| Rating | — | 5.0★ (32) |
| Last release | 9.5 years ago | 26 days ago |
| Current owner | arminmeth | David Anderson / Team Updraft |
| Added to directory | 15 Feb 2017 | 01 Nov 2021 |
| Tested up to | WP 4.7.35 | WP 7.1 |
| Requires PHP | false | 7.2 |
Install figures are rounded by WordPress.org to one significant digit, so a gap smaller than a band step is not a difference. Nothing here ranks the two plugins or recommends either, and no link on this page earns anything.
Why this page is not in search results
There are roughly 1.8 billion possible pairs of WordPress plugins. Generating them would be scaled content abuse, so this registry does not: a comparison renders for anyone who asks for it, and is offered to search engines only once 25 different people have asked for that same pair within 60 days. This one has been requested by 0. Until it crosses, the page works normally but stays out of the index.
Records: Kill JSON REST API · WPGet API – Connect to any external REST API