REST API Enabler vs REST XML-RPC Data — WordPress

REST API Enabler vs REST XML-RPC Data Checker

Name: REST API Enabler
Rating: 5 (3 reviews)

Side-by-side comparison · 24 data points

REST API Enabler

5.0·3reviews·200+installs

wordpress

Change

1. Listing metadata

Field-level data

	REST API Enabler	REST XML-RPC Data Checker
Tagline	—	—
Description	1803 / 5000 chars36% used	2653 / 5000 chars53% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	Mickey Kay	Enrico Sorcinelli
Listed	—	—
Last updated	—	—

2. Categories & rankings

Shared categories on the same row · in-category position inline

REST API Enabler

REST XML-RPC Data Checker

Shared

At a glance

4 metrics · auto-computed

Feature comparison between REST API Enabler and REST XML-RPC Data Checker
Metric	REST API Enabler	REST XML-RPC Data Checker
Rating	5.0 ★	5.0 ★
Total reviews	3	3
Active installs	200+	900+
Free plan	—	—

3. App details

Long-form description · keyword frequency

REST API Enabler

Like this plugin? Please consider leaving a 5-star review. By default, custom post types and custom fields are not accessible via the WordPress REST API. REST API Enabler allows you to: Enable the WP REST API for custom post types and specify WP REST API custom endpoints. Choose which custom fields to include in WP REST API responses for posts, pages, and custom post types. All enabled custom field data is included in the REST API response, nested under the rest_api_enabler key, like so: [ { "id": 179, "date": "2016-07-03T18:06:50", "title": { "rendered": "Test Job" }, . . . "rest_api_enabler": { "custom_meta_1": "Value 1", "custom_meta_2": "Value 2", "custom_meta_3": [ "Array value 1", "Array value 2" ] } } ] Note: prior to verion 1.1.0, all meta keys were included as top-level keys in the API response. Additionally, all values were returned as arrays, regardless of whether the original value was actually an array. This functionality is now deprecated as it risks key-name collisions. Please reference the rest_api_enabler top-level key instead. Usage Activate the plugin, then go to Settings → REST API Enabler in the admin. Click the Post Types tab to enable/disable post types and customize their endpoints. Click the Post Meta tab to enable/disable post meta (custom fields). NOTE: by default, the plugin does not display settings for protected post meta (post meta that begins with an underscore and is intended for internal use only). If you wish to include protected post meta in the plugin settings, you can use the rae_include_protected_meta filter to do so. The following code can be placed in your theme’s functions.php file, or in a custom plugin (on init priority 10 or earlier): add_filter( 'rae_include_protected_meta', '__return_true' );

Top keywords

custom12×4.03%
api11×3.69%
meta10×3.36%
post10×3.36%
rest10×3.36%
rest api10×3.36%
api enabler5×1.68%
enabler5×1.68%
post meta5×1.68%
post types5×1.68%
rest api enabler5×1.68%
types5×1.68%

REST XML-RPC Data Checker

JSON REST API and XML-RPC API are powerful ways to remotely interact with WordPress. If you don’t have external applications that need to communicate with your WordPress instance using JSON REST API or XML-RPC API you should disable access to them for external requests. In the standard WordPress installation JSON REST API and XML-RPC API are enabled by default. In particular the REST API is turned on also for unlogged users. This means that your WordPress instance is potentially leaking data, for example anyone could be able to: copy easily your published contents natively with the REST API (and not with a web crawler); get the list of all users (with their ID, nickname and name); retrieve other information that you didn’t want to be public (such as an unlisted published page or a saved media not yet used). Even if you could do the stuff by writing your own code using native filters, this plugin aims to help you to control JSON REST API and XML-RPC API accesses from the administration panel or programmatically by a simple API filter. Basic Features Disable REST API interface for unlogged users. Disable JSONP support on REST API. Add Basic Authentication to REST API. Remove REST tags, REST Link HTTP header and REST Really Simple Discovery (RSD) informations. Setup trusted users, IP/Networks and endpoints for unlogged users REST requests. Change REST endpoint prefix. Disable XML-RPC API interface. Remove to the Really Simple Discovery (RDS) informations. Remove X-Pingback HTTP header. Setup trusted users, IP/Networks and methods for XML-RPC requests. Show user’s access informations in users list administration screen. Usage Once the plugin is installed you can control settings in the following ways: Using the Settings->REST XML-RPC Data Checker administration screen. Programmatically, by using rest_xmlrpc_data_checker_settings filter (see below). API Hooks rest_xmlrpc_data_checker_settings Filters plugin settings values. apply_filters( 'rest_xmlrpc_data_checker_settings', array $settings ) rest_xmlrpc_data_checker_admin_settings Filter allowing to display or not the plugin settings page in the administration. apply_filters( 'rest_xmlrpc_data_checker_admin_settings', boolean $display ) rest_xmlrpc_data_checker_rest_error Filter JSON REST authentication error after plugin checks. apply_filters( 'rest_xmlrpc_data_checker_rest_error', WP_Error|boolean $result ) xmlrpc_before_insert_post Filter XML-RPC post data to be inserted via XML-RPC before to insert post into database. apply_filters( 'xmlrpc_before_insert_post', array|IXR_Error $content_struct, WP_User $user )

Top keywords

rest22×5.35%
api16×3.89%

Frequently asked

Common questions about this comparison

Which has better reviews, REST API Enabler or REST XML-RPC Data Checker?

REST API Enabler (5.0★, 3 reviews) and REST XML-RPC Data Checker (5.0★, 3 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.

Should I choose REST API Enabler or REST XML-RPC Data Checker?

AppRanks cannot recommend one over the other from published marketplace data: the WordPress Plugin Directory does not expose a rating or review base that separates them. Read both apps' detail pages for the feature breakdown, and compare against your own requirements rather than a headline number.

Which is faster to set up, REST API Enabler or REST XML-RPC Data Checker?

Both apps are one-click installs from the WordPress Plugin Directory. AppRanks doesn't measure setup time directly, and the WordPress Plugin Directory publishes no review base that would let us infer it for these two — read the recent reviews on each app's detail page for user-reported install experience.

Which works better for small vs large WordPress Plugin Directory site owners?

REST API Enabler typically suits early-stage and growth-mode teams based on its published review base (3 reviews). REST XML-RPC Data Checker typically suits early-stage and growth-mode teams based on its published review base (3 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.

Can I migrate data between REST API Enabler and REST XML-RPC Data Checker?

Migration support varies by app and category. REST API Enabler and REST XML-RPC Data Checker both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from REST XML-RPC Data Checker" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

REST API Enabler vs REST XML-RPC Data Checker

REST API Enabler

1. Listing metadata

2. Categories & rankings

REST XML-RPC Data Checker

At a glance

AppRanks verdict

3. App details

Frequently asked

Which has better reviews, REST API Enabler or REST XML-RPC Data Checker?

Should I choose REST API Enabler or REST XML-RPC Data Checker?

Which is faster to set up, REST API Enabler or REST XML-RPC Data Checker?

Which works better for small vs large WordPress Plugin Directory site owners?

Can I migrate data between REST API Enabler and REST XML-RPC Data Checker?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons