What WPGetAPI gets right
WPGetAPI (by David Anderson and Team Updraft, the people behind UpdraftPlus) does one thing very well: it connects WordPress to external REST APIs without code, and puts the returned data on your site. You set up an API and its endpoints in the admin, then output the data anywhere with a shortcode, a template tag, or a Gutenberg block. It handles unlimited APIs and endpoints, every HTTP method (GET, POST, PUT, PATCH, DELETE), query, header, and body parameters, and virtually all authentication methods, including API keys, bearer tokens, basic auth, and OAuth 2.0.
It also goes further than display. You can capture form submissions and send them to an API, format API data into charts and tables, and with its API to Posts add-on, import external data to create or sync WooCommerce products and custom posts on a schedule. It is free at its core, actively maintained, and has a strong reputation for support. If your job is connecting to an API and showing or importing its data, WPGetAPI is purpose-built for it.
The difference: displaying API data versus calling APIs in automations
WPGetAPI is built to pull data in. You point it at an endpoint, and it renders the response on your pages or imports it into your content. That is exactly what you want when an API is a data source for your site.
TrueCommander's APIs module is built to call APIs out, as operations. You save your Stripe, Mailchimp, HubSpot, or webhook endpoints once, then trigger them from the command palette, as a step inside a macro, or on a schedule. The response is mapped into named fields you can feed into the next step, and every call gets a log and a one-click retry. It is the difference between showing what an API returns and using an API to get work done.
The two overlap on the basics: both connect to any REST API with no code, both handle every method and the common auth schemes. Where they part ways is direction and purpose. WPGetAPI renders and imports API data; TrueCommander calls APIs as part of admin automation, alongside its other 100 command variants. Many sites will want both.
{"text":"New order #1247 for $89.00"}step1.ts, step1.channel Shown in advanced mode, where commands start with tp. In easy mode you type the same command without the tp prefix.
See the APIs module in action
A short, unscripted demo of saving an endpoint and calling it from a command, with the response mapped into the next step.
Recordings show the interface at the time of capture and can differ from the current build. Follow this page and the current command reference for supported behavior.
WPGetAPI vs TrueCommander, feature by feature
An honest side by side. They share the no-code API foundation, but they aim in different directions, and WPGetAPI wins outright on getting API data onto your site.
| Feature | WPGetAPI | TrueCommander |
|---|---|---|
| Connect to any REST API, no code | ||
| GET, POST, PUT, PATCH, DELETE with headers and body | ||
| Display API data on the front end (shortcode, template tag, block) | Its core strength | Not its focus |
| Charts and tables from API data | ||
| Import API data into posts or WooCommerce products | API to Posts add-on | |
| Send form submissions to an API | Not its model | |
| Call a saved API from a command palette on demand | ||
| Use an API call as a macro step, mapping the response onward | Chain API calls (Pro) | |
| Run API calls beside other admin operations (backup, email, WooCommerce) | 100 command variants | |
| Call logs and one-click retry | Action logs (Pro) | |
| Price | Free core + paid Pro / add-ons | $59/year, everything included |
| Maintenance | Current release details on the official site, recent release | Current release details on the official site |
Product features, editions, pricing, and compatibility can change. Consult the linked official product listing before choosing; this page does not promise the accuracy of an old installation, rating, or release snapshot.
When WPGetAPI is the right pick
For getting API data onto your site, WPGetAPI is the better tool, and we would point you to it ourselves. Choose it when:
- You want to display external API data on your pages with a shortcode, template tag, or block.
- You want charts or tables built from a live API feed.
- You need to import API data into posts or WooCommerce products and keep them synced (its API to Posts add-on).
- You want to send form submissions from Contact Form 7, WPForms, or Gravity Forms to an API.
- You want a free core, deep authentication support including OAuth 2.0, and a tool focused on doing API connections well.
When to choose TrueCommander
TrueCommander is the better fit when an API call is a step in your work, not a data feed for your pages:
- You want to call a saved API on demand from a keyboard palette, or on a schedule.
- You want an API call to be one step in a macro, with its response mapped into the steps that follow.
- You want those calls to sit beside other operations, charge through Stripe, then email a receipt, then post to Slack, in one flow.
- You want call logs and one-click retry built in, as part of a broader 100-variant catalogue.
They work well together. Plenty of sites use WPGetAPI to display or import API data, and TrueCommander to call APIs inside their automations. The two solve different halves of the problem and do not conflict.