How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Capitalist API

The current Capitalist API — published as the "Integration API" — enables programmatic mass payouts, currency and digital-asset conversion, and balance, transaction and merchant-order reporting across Capitalist's supported payment systems. It is a JSON-over-HTTPS REST surface at https://api2.capitalist.net that creates and tracks outbound payouts across roughly 45 payment channels (cards, bank transfers, mobile operators, fast payment systems, e-wallets and cryptocurrencies), issues ephemeral cryptocurrency deposit addresses, and runs end-user KYC. Every request carries three headers — API-Key, X-Request-Timestamp and a SHA-256 signature over the timestamp, the raw body and the API secret — and payment outcomes are delivered to a per-request callbackUrl signed the same way. It is designed for businesses that need to pay large numbers of recipients (affiliates, freelancers, publishers) without maintaining separate accounts in each underlying payment system.

Capitalist API is one of 2 APIs that Capitalist publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Bulk Payouts, Cryptocurrency, KYC, Mass Payments, and Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 6 paths, organized into 4 resource areas, and defines 52 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://api2.capitalist.net.

6 operations 6 paths 52 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api2.capitalist.net
Resource Areas
4

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 4 GET, 2 POST. They span 4 resource areas: account, exchange, payment, rate. Each is listed below with its method, path, parameters, and response codes.

account 1
GET
/v1/account/list
- account
1 param → 200400
exchange 1
POST
/v1/exchange
- exchange
body → 200400
payment 3
POST
/v1/payment
- payment
body → 200400
GET
/v1/payment/document/{documentId}
- payment
1 param → 200400
GET
/v1/payment/{userRequestId}
- payment
1 param → 200400
rate 1
GET
/v1/rate
- rate
2 params → 200400

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are WORLDCARDEUR (12 properties), EUR_NETELLER (12 properties), WORLDCARDUSD (12 properties), EUR_SKRILL (12 properties). Each schema is shown below with its type and property counts.

YANDEX
object
2 properties 2 required
PAYONEER_EUR
object
2 properties 2 required
GCASH
object
8 properties 8 required
BITCOIN
object
2 properties 2 required
EUR_SKRILL
object
12 properties 11 required
MEGAFON
object
2 properties 2 required
AZCARD
object
Azerbaijani cards / карты Азербайджана
7 properties 7 required
COBANK
object
5 properties 5 required
UKR_MOBILE
object
2 properties 2 required
QIWI
object
2 properties 2 required
PaymentPayload
WORLDCARDEUR
object
12 properties 12 required
GCashReceiver
object
3 properties 3 required
IMPS
object
4 properties 4 required
CreateConversionDocumentRestRequest
object
3 properties 3 required
CreatePaymentIntegrationResponse
object
1 property 1 required
TRCARD
object
5 properties 5 required
WithdrawalStateResponse
object
11 properties 10 required
SimpleError
object
1 property 1 required
GCashSender
object
1 property 1 required
SBP
object
8 properties 8 required
THAILAND_BANK
object
4 properties 4 required
USDTTRC20
object
2 properties 2 required
CreatePaymentIntegrationRequest
object
7 properties 5 required
EUR_NETELLER
object
12 properties 12 required
YOTA
object
2 properties 2 required
USDTERC20
object
2 properties 2 required
BRBANK
object
5 properties 5 required
RUCARD
object
7 properties 7 required
ETH
object
2 properties 2 required
SOUTH_KOREA_BANK
object
4 properties 4 required
MALAYSIA_BANK
object
4 properties 4 required
BEELINE
object
2 properties 2 required
ARBANK
object
Argentinian banks / банковские счета Аргентины
4 properties 4 required
BankRecipient
object
8 properties 8 required
UZCARD
object
3 properties 3 required
TMOBILE
object
2 properties 2 required
BankDestination
object
3 properties 3 required
USDCERC20
object
2 properties 2 required
WORLDCARDUSD
object
12 properties 12 required
RUCARDP2PDYN
object
6 properties 6 required
PAYTM
object
2 properties 2 required
KZCARD
object
5 properties 5 required
TELE2
object
2 properties 2 required
PAYONEER
object
2 properties 2 required
RUCARDP2P
object
6 properties 6 required
INDONESIA_BANK
object
4 properties 4 required
PAYONEER_USD
object
2 properties 2 required
ShortAccount
object
4 properties 4 required
MTS
object
2 properties 2 required
UKRCARD
object
4 properties 4 required
GECARD
object
7 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

capitalist-integration-api-openapi.json Raw ↑

Other APIs Capitalist publishes across the network.

Capitalist Payments API (v1, deprecated)
Where this information came from

This is an independent, third-party profile of Capitalist API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.