Custom API for WP

75 Quality Score

Active Installs

14/30

A 45 out of 30 popularity score is unusual: the active install count is only about 1,000, which is low for this category, but the ratio of installs to ratings and the breadth of tagged use cases kept the sub-score healthy.

Update Freshness

25/25

Maintenance scored a perfect 100 out of 25, with a last-updated stamp of June 2026 and compatibility tested against WordPress 7.0, which signals an actively maintained codebase rather than an abandoned tool.

User Rating

14/15

User ratings are strong at 96 out of 100 across 45 reviews, suggesting the small user base that has tried it is genuinely satisfied with the no-code endpoint builder.

Support Health

8/15

Support health sits at 50 out of 15 because there are zero support threads on record, which means there is no public track record of the developer responding to issues or bug reports.

WP Compatibility

15/15

Compatibility scored a perfect 100 out of 15, with a stated minimum of WordPress 3.0.1 and PHP 5.4, so it will run on virtually any WordPress environment, though in practice you would want a current PHP version for security.

Scores higher than 41% of indexed plugins

About

Connect WordPress with External APIs and create no-code custom WordPress REST API endpoints to interact with the WordPress database to perform SQL ope …

Active Installs 1k+

Rating ★★★★½ 4.8/5

Last Updated 2026-09-28 5:19am GMT

Requires WordPress 3.0.1+

Tested Up To 7.0.6

Requires PHP 5.4+

Security History

2 known vulnerabilities, all patched

2 High

Most recent: July 28, 2025

View details ▸

What It Does

Custom API for WP lets site owners build no-code REST API endpoints for reading and writing to the WordPress database, and it also connects WordPress to external APIs for pushing and pulling data. In practice, it turns a WordPress install into a backend service that mobile apps, CRMs, and other platforms can talk to without writing PHP.

Who It's For

This is a good fit for developers or technical marketers running headless WordPress setups, mobile app backends, or inventory and order workflows where the default REST API does not cover the data shape needed. It is also useful for small agencies that need to spin up custom endpoints for clients without building a bespoke plugin each time.

Who Should Skip It

If you only need to expose standard WordPress content (posts, pages, users, custom post types) to a frontend, the core REST API or WPGraphQL already covers that with far more community vetting. Non-technical site owners should also skip this, because configuring custom SQL-backed endpoints still requires a clear understanding of what data is being exposed and to whom.

The Bottom Line

Custom API for WP fills a real gap for no-code custom REST endpoints and SQL-backed reads and writes, and its maintenance and rating signals are genuinely strong. The main caveat is the tiny install base and the absence of any public support history, so you are trusting a single developer with very little community oversight. Try it on a staging site first, and have a backup plan if the project goes quiet.

Related Plugins

WPGraphQL 82/100

Choose WPGraphQL when your frontend is a JavaScript framework that prefers GraphQL queries over REST, and you mainly need to read WordPress content rather than expose custom SQL operations.

JWT Authentication for WP REST API 82/100

Pick this when your main concern is securing existing REST endpoints with token-based authentication rather than building new custom endpoints.

Disable WP REST API 81/100

This is the opposite use case: choose it when you want to lock down the REST API entirely on a site that does not need external access.

WPGet API 80/100

WPGet API is a closer functional match, so pick it instead if your priority is consuming data from external REST APIs in WordPress rather than exposing WordPress data to outside systems.