WPGet API – Connect to any external REST API
View on WordPress.orgScores higher than 81% of indexed plugins
About
Connect any REST API to WordPress. WPGet API enables easy API integration, allowing you to display API data without any code.
Security History
What It Does
WPGet API lets you connect any external REST API to WordPress and display the returned data on your site without writing code. It handles endpoints, authentication, and template tags so you can pull in things like weather, property listings, or stock prices through shortcodes or the block editor. The free version covers single-call requests, with the paid tier adding features like format conversion and cached responses.
Who It's For
This plugin is best for site owners and developers building content-driven sites that depend on third-party data feeds, such as real estate listings, sports scoreboards, news aggregators, or crypto price trackers. It works well for non-coders who need a clean admin UI to map API fields to page content, and for small agencies that want a repeatable way to wire up REST sources across multiple client builds.
Who Should Skip It
If your project needs GraphQL, SOAP, or webhook-driven workflows, this plugin is the wrong tool since it is strictly REST-focused. Anyone comfortable writing a few lines of PHP or JavaScript will get more control and better performance using wp_remote_get directly in a custom theme or child plugin.
The Bottom Line
WPGet API scores 80.41/100 and does exactly what it promises: a low-code bridge between WordPress and external REST services, backed by recent updates and a clean compatibility profile. The lack of public support threads is a real gap, so evaluate it on a staging site before relying on it for production traffic. For straightforward read-only API integrations it is a strong pick, but heavy or mission-critical data pipelines will still benefit from custom code.
Related Plugins
Pick this instead if your real need is bulk URL export or redirect management rather than consuming external REST data.
Choose this instead if you want to lock down WordPress's own REST endpoints for security, not connect to third-party APIs.
Go with this for transactional email delivery via the Mailgun REST API rather than for displaying arbitrary external data.
Choose this when you need to speed up WordPress's built-in REST responses, not call external services.
Pick this if you need to authenticate external apps against your own WordPress REST API rather than call out to remote APIs.