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

Tango Funding API

Fund accounts via credit card deposits and fund transfers

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

Tagged areas include Funding. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.

This API exposes 6 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: https://api.tangocard.com/raas/v2, https://integration-api.tangocard.com/raas/v2.

6 operations 5 paths 6 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.tangocard.com/raas/v2
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Tango Funding API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Auth using platform credentials (username/password)

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Funding 6

Fund accounts via credit card deposits and fund transfers

POST
/creditCardDeposits
Create Credit Card Deposit
createCreditCardDeposit body → 201
GET
/creditCardDeposits/{depositId}
Get Credit Card Deposit
getCreditCardDeposit 1 param → 200
GET
/creditCards
List Credit Cards
listCreditCards → 200
POST
/creditCards
Register Credit Card
registerCreditCard body → 201
GET
/creditCards/{token}
Get Credit Card
getCreditCard 1 param → 200
GET
/transferFunds
List Fund Transfers
listFundTransfers → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are FundTransfer (7 properties), CreditCardDeposit (7 properties), Address (6 properties), CreditCard (5 properties). Each schema is shown below with its type and property counts.

RegisterCreditCardRequest
object
4 properties 4 required
CreditCardDepositRequest
object
4 properties 4 required
CreditCard
object
5 properties
Address
object
6 properties
CreditCardDeposit
object
7 properties
FundTransfer
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tango-funding-api-openapi.yml Raw ↑

Other APIs Tango publishes across the network.

Tango Accounts API
Tango Catalog API
Tango Customers API
Tango Digital Templates API
Tango Line Items API
Tango Low Balance Alerts API
Tango Orders API
Tango Reference Data API
Where this information came from

This is an independent, third-party profile of Tango Funding 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.