⭐ Independent review

Capitalist API 2026

The Capitalist API exposes the platform's wallet, payout, and card-management features to backend systems. Affiliate networks use it for automated payouts, media-buyer agencies for programmatic card creation, and online businesses for vendor and contractor payments.

This page summarises what the API does, the main resource families, and typical integration patterns. For exact endpoint paths, schemas and rate limits, always refer to the official Capitalist developer documentation — details change between versions.

Capitalist API 2026 - Mass Payments & Integration Guide | Capitalist.casa

Open a Free Capitalist Account →

What the API covers

At a high level, the Capitalist API exposes four resource families:

Account / wallet — balances, transaction history, currency conversion.
Payouts — single and bulk outgoing transfers to Capitalist users, bank cards, bank accounts and crypto addresses.
Cards — issue, fund, defund, freeze and close virtual cards programmatically.
Webhooks — push notifications when deposits, payouts or card transactions change state.

Authentication

The API uses API keys scoped to a Capitalist account, typically combined with a signed request mechanism (request-body signature plus key ID). Keep keys in a secrets manager, restrict them by IP where the dashboard allows, and rotate periodically.

Mass payments — the headline use case

The mass-payment endpoint accepts an array of payout instructions in a single request. Each instruction specifies recipient, method (internal Capitalist user, card, bank, crypto), currency and amount. The platform validates, queues and reports per-item status.

Practical pattern: an affiliate network triggers nightly payouts by uploading a payouts batch via API, then listens for webhook callbacks per item to mark its internal payout records as paid or failed.

Card issuance automation

For ad agencies running many campaigns, the cards API lets you issue a fresh virtual card per campaign and defund it when the campaign ends. Limits, currency and metadata travel as part of the issuance payload, so the card can be tagged for accounting.

Webhooks and idempotency

Always pass an idempotency key on writes to avoid duplicate payouts on retries. Subscribe to webhooks for transaction state changes; trust the webhook as the source of truth rather than the initial response, since some methods settle asynchronously.

Rate limits and reliability

The platform applies per-account rate limits. Build your integration with backoff, batching and a queue, especially for nightly bulk payouts. Monitor failure rates per payout method — bank-card payouts can occasionally bounce and need a retry with a different method.

FAQ

Is the Capitalist API free to use?

API access is included with a Capitalist business account in most plans. Per-transaction fees still apply according to method (card payout, bank, crypto, internal).

Can I issue cards via API on a personal account?

Programmatic card issuance is typically a business-account feature. Check the current dashboard for your account type and what scopes the API key supports.

Does the API support crypto payouts?

Yes — payouts to supported cryptocurrencies are exposed alongside fiat methods. Confirm the current supported assets and network choices in the developer docs.

How do I handle FX in mass payments?

Convert in the wallet first to the target currency, then pay out — or pay out in source currency and let the recipient method handle conversion. Most predictable for accounting is converting beforehand.