API Forge Connector
WordPress API pluginBuild powerful APIintegrations for WordPress.
API Forge Connector links external REST APIs to your site. Configure requests, authenticate, test responses and display live data with a block or a shortcode, instead of rebuilding a custom integration from scratch.
- Version 1.3.0
- WordPress 5.9+
- PHP 8.0+
- GPL licensed
api.weatherapi.com/v1/current.json
?q=london&key={{const.APIFORGE_API_KEY_WEATHER}}
{ "current": { "temp_c": 21.3, … } }
current.temp_c
[apiforge_api endpoint="weather" json_path="current.temp_c"]
Today in London: 21.3°C
The problem
The data your site needslives somewhere else.
The booking system knows what is available. The inventory system knows what is in stock. The CRM knows the account, the SaaS platform knows the price, and the internal service knows the number your team quotes on the phone. None of them is WordPress, and the website is where customers actually look.
Traditionally, closing that gap means custom development: a developer writes a bespoke integration for one endpoint, and the next data point is another ticket, another deployment, another thing only they can maintain. API Forge Connector turns that into configuration — the connection, the authentication, the caching and the display are set up once, in the admin, and reused for the next API.
What it does
A configurable bridgebetween WordPressand REST APIs.
Point API Forge Connector at a REST endpoint, give it the credentials the API expects, and test the call from inside WordPress. Once the response looks right, pick the values you want with a JSON path and place them on a page with [apiforge_api] or the Gutenberg block. What renders is the live answer from the source, cached for as long as you say it should be.
It is not a no-code claim for every case. The standard read-and-display workflow genuinely needs no code. Advanced work — custom loop templates, hooks, JavaScript triggers, programmatic endpoints — is where PHP and JavaScript still earn their place, and there is a documented developer API waiting for it.
Who it’s for: site owners who need external data on their pages without a development project, and the developers and agencies who would rather configure an integration in an afternoon than write and maintain one for every client.
How it works
Five steps,start to page.
Connect
Enter the API endpoint and the authentication it expects — an API key, a bearer token, basic auth, or OAuth 2.0 on Pro.
Configure
Add query parameters and headers. Free sends GET requests; Pro adds POST, PUT, PATCH and DELETE with a request body.
Test
Send the request from the admin and read the raw response, status code and timing before anything touches a page.
Pick
Point a JSON path at the value you want, or fetch the response in the block and click Add next to it. Pro’s response mapper lays data out in your own HTML template.
Display
Place the data with the [apiforge_api] shortcode or the Gutenberg block. Pro loops arrays through your own template.
Nested values are a path away: [apiforge_api endpoint="weather" json_path="current.temp_c"] reaches into the response and prints exactly the value you asked for.
Inside the plugin
The whole workflow isin the WordPress admin.



Use cases
All of these are API connections, not native integrations: if the system exposes a REST API and you have credentials for it, API Forge Connector can call it and render what comes back.
What people connect.
Live pricing
Rates that change on the source system — currency, commodities, tariffs — read from its API instead of retyped into a page each week.
Availability
Stock levels, seats or slots pulled from the booking or inventory platform that owns them, if it exposes a REST API.
Product information
Specs, catalogue fields or media served from a PIM, headless CMS or store API and rendered inside your WordPress layout.
CRM and business data
Counts, statuses or account details from the CRM or internal service, shown on a member page or an internal dashboard.
Market and public data
Weather, exchange rates, transport or open-government feeds — the public APIs a marketing page keeps wanting.
Internal business APIs
The service your team already built. Point an endpoint at it, authenticate, and it renders like any other content.
External content
Posts, events or listings held in another platform, displayed here without a second CMS to maintain.
Features
Everything theplugin can do.
Anything marked Pro needs a licence. Everything else is in the free version.
Requests
- Unlimited endpoints
- GET requests with query parameters and headers
- Endpoint testing with the raw response
- POST, PUT, PATCH and DELETE with a request bodyPro
Authentication
- API key, in a header or the query string
- Bearer token and basic auth
- Keys encrypted, or kept in wp-config.php
- OAuth 2.0 with automatic token refreshPro
Data
- JSON path extraction
- One filter to pick an item from a list
- Dynamic variables: user ID, API key, wp-config constants
- Arrays and lists with custom templatesPro
- Response mapper with your own HTML templatePro
- Several filters combined with ANDPro
- Post, query string, date and site variablesPro
WordPress
- Gutenberg block with a visual field picker
- [apiforge_api] shortcode, live on the front end
- Works in Elementor and other builders
- [apiforge_api_loop] for repeating templatesPro
Performance
- Response caching with a per-endpoint lifetime
- Per-placement cache override
- Fallback content when a request fails
- Conditional caching rules by status or contentPro
Developer
- PHP API for fetching and registering endpoints
- Hooks and filters throughout
- Request logging, with credentials masked
- Request replay from the log
Automation
- Cron-scheduled requestsPro
- WordPress hook triggersPro
- JavaScript event triggersPro
- Email notification when a trigger failsPro
For developers
A real PHP API underneaththe interface.
Everything the admin does is available in code. apiforge_get_endpoint_data() fetches from a configured endpoint with caching and JSON paths, apiforge_register_endpoint() creates endpoints programmatically, and apiforge_test_endpoint(), apiforge_clear_endpoint_cache() and apiforge_extract_json_path() cover the rest of the round trip.
// Fetch a value from a configured endpoint, cached
$temp = apiforge_get_endpoint_data( 'weather', [
'json_path' => 'current.temp_c',
'cache' => 'default',
] );
// Reshape a response before anything renders it
add_filter( 'apiforge_endpoint_data', function ( $data, $endpoint, $args ) {
return $data;
}, 10, 3 );
// Create an endpoint in code
apiforge_register_endpoint( 'rates', [
'url' => 'https://api.example.com/v1/rates',
] );Filters
apiforge_endpoint_data,apiforge_shortcode_html_output,apiforge_rest_public_accessandapiforge_pre_requestintercept the data, the markup, the public route and the outgoing request.Actions
apiforge_plugin_initializedandapiforge_endpoint_registered, plusapiforge_trigger_executedandapiforge_trigger_failedon Pro, give you somewhere to hang your own logic.JavaScript events
A Pro trigger fires a configured request from a JavaScript event on the front end, for endpoints you have explicitly enabled for that use.
Caching and responses
Cache strategy is per call —
default,no-cacheorforce-refresh— and failures come back as aWP_Erroryou can handle.
The honest ceiling. API Forge Connector connects, displays, and on Pro writes and automates. What it is not is a full integration project: two systems kept reconciled, business rules, data moving across a whole stack. That is custom work, and it is the other thing this studio does — what custom API integration covers.
Free vs Pro
The free version is a complete workflow for reading and displaying API data, not a trial — nothing in it expires or is capped. Pro is a separate plugin for write requests, loops, OAuth 2.0 and automation.
Start free. Upgrade whenthe work asks for it.
| Feature | Free | Pro |
|---|---|---|
| Endpoints | Unlimited | Unlimited |
| GET requests | Included | Included |
| POST, PUT, PATCH, DELETE | Not included | Included |
| API key, token, basic auth | Included | Included |
| OAuth 2.0 | Not included | Included |
| Encrypted credentials | Included | Included |
| JSON path and one filter | Included | Included |
| Combined filters | Not included | Included |
| Shortcode and block | Included | Included |
| Lists and loops | Not included | Included |
| Response mapper | Not included | Included |
| Response caching | Included | Included |
| Conditional cache rules | Not included | Included |
| Endpoint test panel | Included | Included |
| Request logs and replay | Included | Included |
| Automation triggers | Not included | Included |
| Support | Community | Priority |
Every Pro plan carries the same features. The only difference is how many sites the licence covers: $49.88 a year for 1 site, $119.88 a year for 5 sites and $167.99 a year for 20 sites.
Pricing
Priced by sites.Monthly, yearly or lifetime.
Pro is sold through Freemius, which handles checkout, tax, licences and premium updates. Choose monthly, yearly or a one-time lifetime licence at checkout.
Business
Most popular$119.88
5 sites
A live site plus staging, or a small portfolio you own.
Built to be trusted with credentials
The parts you’d only noticeif they were missing.
Credentials handled properly
Keys are encrypted with AES-256-GCM using your own WordPress salts before they are stored — or define a wp-config.php constant and they never enter the database at all. Either way they are masked in the logs.
Nothing public by accident
The plugin registers a REST route per endpoint, and it is off until you enable it for that specific endpoint. Configured APIs are not exposed to visitors by default.
Cached, and quiet about it
Each endpoint has its own cache lifetime — an hour by default, zero to disable — and request logging runs asynchronously, so neither one sits in the way of a page load.
Predictable when an API fails
Cached data is served where it exists, your fallback text renders where it does not, and the error goes to the request log instead of the page.
Plays with the stack you have
WordPress 5.9+ (tested to 7.1), PHP 8.0+, GPLv2 or later. WooCommerce HPOS compatibility is declared, and shortcodes render in Elementor and other page builders.
Uninstalls completely
Deleting the plugin removes its options, tables, scheduled events and log files, on single sites and multisite alike. Switching between Free and Pro keeps everything.
Common questions
Plugin support: support@cleardigitalstudio.com
A WordPress plugin that connects your site to external REST APIs. You configure an endpoint in the admin, test it, choose the data you want with a JSON path, and display it with a shortcode or a Gutenberg block. The free version is a complete workflow for reading and displaying API data; Pro adds write requests, loops, OAuth 2.0 and automation.
REST APIs that return JSON: public APIs, SaaS platforms such as Airtable, and your own internal or custom backends, with API key, bearer token or basic authentication (OAuth 2.0 on Pro). Built-in templates set up OpenWeather, CoinGecko and Airtable in a few clicks.
The free version sends GET requests, which is what reading and displaying data needs. POST, PUT, PATCH and DELETE, with request bodies, are in Pro.
Not for the standard workflow. Endpoints are configured and tested visually, and the shortcode is generated for you. Coding starts to matter for advanced work — custom loop templates, hooks, JavaScript triggers — and there is a documented PHP API for exactly that.
Yes. Pick a value with a JSON path and place it in any post, page or builder layout. Pro adds the loop shortcode, which repeats your own template for each item in an array.
Yes. A block ships in the free version with an endpoint selector, so data can be placed in the editor without touching a shortcode.
[apiforge_api] is the free shortcode and [apiforge_api_loop] is the Pro one for lists. Both render in the block editor, the classic editor, and any page builder that supports shortcodes, including Elementor.
Unlimited endpoints, GET requests with parameters and headers, bearer token, API key and basic authentication, encrypted credential storage or wp-config.php constants, JSON path extraction with a filter, the [apiforge_api] shortcode, the Gutenberg block, configurable caching, the test panel, and request logs with replay. Every feature works without registration, payment or a time limit.
Pro is a separate plugin that adds POST, PUT, PATCH and DELETE with request bodies; the loop shortcode with custom templates; filters combined with AND; the response mapper; OAuth 2.0 with automatic token refresh; conditional caching rules; automation triggers on cron, WordPress hooks and JavaScript events, with email notification on failure; more dynamic variables; and priority email support.
Pro is sold and delivered through Freemius. A licence covers a set number of sites — one on Personal, five on Business, twenty on Agency — and you can pay monthly, yearly, or once for a lifetime licence. After checkout you download API Forge Connector Pro, install it, and activate the licence key from the WordPress admin.
Yes. apiforge_get_endpoint_data() fetches from a configured endpoint with caching and JSON paths, apiforge_register_endpoint() configures endpoints in code, and filters such as apiforge_endpoint_data and apiforge_shortcode_html_output let you reshape the data or the markup before it renders.
Every endpoint has its own cache lifetime, one hour by default, and zero disables it. A single placement can override that with cache="no-cache" or cache="force-refresh". Caching only on certain status codes or response contents is a Pro rule.
The free version is a public WordPress.org plugin with no limit on sites or endpoints. Pro licences are counted per site: Personal covers one, Business five, Agency twenty.
Nothing is deleted: endpoints, settings, credentials, logs and shortcodes stay exactly as they are, and everything in the free version keeps working. An active licence is what entitles you to premium updates and priority support. A lifetime licence never expires. Renewal terms are shown by Freemius at checkout.
Get started
Connect your firstAPI today.
Start free, and add Pro when you need write requests, loops or automation.