APIs Module

Every API call you make, saved as a button.

Q: How does response field mapping work?

Enter a dot-separated response path such as 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.

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

Restrict access to saved auth headers Chain into any macro Every call logged

APIs

Need help?

Total APIs 12 10 enabled

Total calls 8,247 7,994 successful

Success rate 96.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

Interface examples use sample data. Results, counts, and timing vary by site and configuration.

See it in action

Connect any API, zero code.

A short walk-through of the APIs module: register an external endpoint once, map its response fields, and invoke it through send api in supported execution contexts. Use Variables for non-secret values only. Restrict access to saved credentials and review request logs. No glue code.

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.

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 tracked Logged, 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 tabresponse path 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.

Map supported dot/bracket response paths to named scalar outputs for later macro steps. This is not a full JSONPath query language. Reserved receipt fields cannot be overwritten.

response path 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.

Real examples

The same command, every service.

Save the endpoint once in the APIs module, then call it with send api from a command, macro, or schedule. Four common ones:

Stripe, create a chargePOST to https://api.stripe.com/v1/charges with a Bearer secret key. Map the response to charge_status and receipt_url, then branch to a refund on failure or email the receipt on success. Call it with tp send api → "Stripe charge".

Mailchimp, subscribe a memberPOST to /3.0/lists/{list_id}/members with basic auth and your API key. Pass the customer email and merge fields from the trigger, so a new WooCommerce order adds the buyer to a list automatically. Call it with tp send api → "Mailchimp subscribe".

HubSpot, create or update a contactPOST to /crm/v3/objects/contacts with a private-app token. Send name, email, and lifecycle stage from your form or order data to keep the CRM in sync. Call it with tp send api → "HubSpot upsert contact".

Any webhook, post a JSON payloadPOST a JSON body to a Slack, Discord, or Make/Zapier webhook URL, no auth needed for most. Fire a team alert the moment an order is paid or a form is submitted. Call it with tp send api → "Slack #orders".

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?

Saved API configuration can contain credentials in its headers or body. Restrict access and review exports and logs. Variables are visible non-secret data and must not hold passwords, private keys, or access tokens.

What auth patterns are supported?

Configure method, URL, headers, and body for supported HTTP requests. A pre-issued bearer or API token can be entered in the appropriate field. The module does not implement an OAuth authorization or refresh flow for every provider.

How does response field mapping work?

Enter a dot-separated response path such as 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.