APIs Module

Every API call you make,saved as a button.

Stop pasting curl into terminals. Save your Stripe, Mailchimp, HubSpot and webhook endpoints once. Call them from macros. Map response fields into chain results. Full logs, one-click retry.

Save your first API View all modules

Auth headers stored securely Chain into any macro Every call logged

APIs

Need help?

Total APIs1210 enabled

Total calls8,2477,994 successful

Success rate96.9%last 30 days

Create API

View Logs

Name	Method	Category	Last status
stripe create charge	POST	payments	200
mailchimp add subscriber	POST	marketing	200
hubspot get contact	GET	crm	200
slack post message	POST	notifications	200
zapier webhook trigger	POST	automation	429

The Problem

Your integrations live in a scratch folder.

You test an endpoint in a terminal tool. It works. You paste it into code, and it works. Six months later, the API changes, the code breaks, and nobody remembers where the original request lived.

Without the APIs module

Open a terminal or HTTP client. Paste your URL, auth, body again

Hardcode the endpoint into a plugin or functions.php

API key lives in plaintext in a commit history somewhere

No logs. No idea when it last ran or what it returned

Can't reuse from a macro, schedule, or keyboard shortcut

Credentials leaked Rebuild every time No visibility

With the APIs module

Save every endpoint once with method, URL, headers, body

Auth headers reference Variables module tokens, not hardcoded keys

Call from any macro, schedule, or shortcut with one step

Map response fields into chain results for downstream steps

Every call, saved and trackedLogged, filterable, retryable. Built into the plugin.

Centralized Reusable Full audit trail

Full-featured builder

Four tabs. One full editor.

Method picker. URL bar. JSON, form-encoded, or raw bodies. Headers. Response mapping. Test console. All inside WordPress.

Body tabJSON, form-encoded, raw, or none. Full token substitution inside.

Headers tabKey-value rows. Auth headers reference Variables module tokens.

Response Mapping tabJSONPath to field name. Extracted values become chain results.

Test tabClick Send Test. See the response pretty-printed. No guesswork.

Create API

Response mapping

Pick the fields you actually need.

Most API responses return 50 fields. You need 3. Map them by JSONPath. They become named chain results the next macro step can use.

JSONPath syntaxDot notation and array indexes. data[0].user.id just works.

Named chain resultsDownstream steps reference {{step1.stripe_id}} directly.

Reserved name guardNames like success and status_code stay protected.

Inline validationBad field names turn red before you can save.

Built for macros

Drop it into any flow.

The send api command is a macro step. Pick your saved API, and mapped response fields flow into the next step like any other chain result.

Trigger-poweredWooCommerce order, user register, post published. Data flows straight into your API call.

Runs on schedulesHourly health pings, nightly data syncs, any cron interval.

Loop over arraysOne API call per line item with @loop blocks in the body.

Branch on statusResponse mapped to charge_status. Branch to refund on failure.

Full audit trail

Every call, logged and searchable.

When an integration fails at 3 AM, you need to know exactly what was sent, what came back, and how long it took. All of it, one click away.

Request body capturedSee the exact payload sent, with tokens already resolved.

Response body storedFull response, status code, duration in milliseconds.

Filter by everythingAPI, status, source (macro or manual), date range.

Traced to the macroEach log shows which macro fired the call. Debug in context.

The Math

One place. Every integration.

No more scattered endpoints across plugins, code snippets, and terminal scratch files.

GET, POST, PUT, PATCH, DELETE

Every HTTP method, body type, and auth pattern covered

Callable from macros, schedules, shortcuts

Save once, trigger anywhere inside TrueCommander

Of calls logged

Request, response, duration, source. Nothing silent.

$59/yr

One license. Every integration centralized. And APIs is just one of ten modules. See pricing

FAQ

Questions? Answered.

Where are API keys stored?

API keys live in headers or body fields, stored in the plugin's database. The recommended pattern is to keep keys in the Variables module and reference them as {{var.stripe_key}} in your header values. That way one rotation updates every API that uses it.

What auth patterns are supported?

Any pattern that sets headers. Bearer tokens, Basic auth, custom API-key headers, OAuth-signed requests. All work through standard header key/value rows. The plugin doesn't generate OAuth flows for you, but any pre-generated token drops in fine.

How does response field mapping work?

Enter a JSONPath like data.user.id and give it a chain-field name like user_id. After the call, downstream macro steps reference {{step1.user_id}} the same way they'd reference any other step's output. Reserved names (success, status_code, body, duration_ms) are protected.

Can I test an API before saving it into a macro?

Yes. The Test tab inside every API editor sends a real request with your typed values and shows the pretty-printed response. Also, the APIs table has a Run Now action per row, so you can re-test any saved API on demand and the call appears in the logs like any other.

Ready?

Stop building the same API call twice.

Save your integrations once. Call them from anywhere. See every response.

Save your first API View all modules

14-day money-back guaranteeWe stand behind TrueCommander. If it's not the right fit within 14 days, request a refund through our support. Terms apply per our refund policy.