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

Cable transactions API

The transactions API from Cable — 4 operation(s) for transactions.

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

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 11 operations across 4 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.cable.tech, https://transaction-api.cable.tech.

11 operations 4 paths 19 schemas 1 DELETE2 GET4 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.cable.tech
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Cable transactions API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 11

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

transactions 11
GET
/v2/transaction
Check if a transaction exists
check-transaction 2 params → 200401404429500
POST
/v2/transaction
Add a new transaction
add-transaction 1 param body → 201400401409429500
PUT
/v2/transaction
Update an existing transaction
update-transaction 1 param body → 200400401404429500
DELETE
/v2/transaction
Submit a deletion request for a transaction and any related data
delete-transaction 1 param body → 200401404429500
POST
/v2/transactions/batch
Add transactions in batch
add-transactions-batch 1 param body → 200400401429500
PUT
/v2/transactions/batch
Update transactions in batch
update-transactions-batch 1 param body → 200400401404429500
GET
/transaction
Check if a transaction exists
check-transaction 2 params → 200401404429500
POST
/transaction
Add a new transaction
add-transaction 1 param body → 201400401409429500
PUT
/transaction
Update an existing transaction
update-transaction 1 param body → 200400401404429500
POST
/transactions/batch
Add transactions in batch
add-transactions-batch 1 param body → 200400401429500
PUT
/transactions/batch
Update transactions in batch
update-transactions-batch 1 param body → 200400401404429500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are NewTransactionRequest (13 properties), UpdateTransactionRequest (13 properties), NewTransactionRequest_2 (12 properties), UpdateTransactionRequest_2 (12 properties). Each schema is shown below with its type and property counts.

NewTransactionRequest
object
Transaction data to add. Required fields include: timestamp, txid, type, method, amount, currency, and status. Identity requirements: - At least one of 'sender…
13 properties 7 required
UpdateTransactionRequestMethod
string
Payment method used for the transaction. Required when creating new transactions, optional for updates. Each method may have different processing times, fees,…
WriteOperationResponse
object
4 properties 4 required
BatchNewTransactionRequest
array
NewTransactionRequestStatus
string
Transaction status. Required when creating new transactions, optional for updates.
Transactions_checkTransaction_Response_200
object
4 properties
GeneralError
object
3 properties 2 required
NewTransactionRequestMethod
string
Payment method used for the transaction. Required when creating new transactions, optional for updates. Each method may have different processing times, fees,…
GeneralErrorErrorsItems
object
2 properties
NewTransactionRequestType
string
Transaction type. Required when creating new transactions, optional for updates.
BatchUpdateTransactionRequest
array
Transactions_deleteTransaction_Response_200
object
2 properties
UpdateTransactionRequest
object
Transaction data to update, referenced by 'txid'. The 'timestamp' field represents the update time. Only the fields to be updated need to be included.
13 properties 2 required
UpdateTransactionRequestType
string
Transaction type. Required when creating new transactions, optional for updates.
UpdateTransactionRequestStatus
string
Transaction status. Required when creating new transactions, optional for updates.
NewTransactionRequest_2
object
Transaction data to add. All fields are required except for 'amountusd', which will be calculated using the latest exchange rate if not provided. The 'timestam…
12 properties 10 required
UpdateTransactionRequestMethod_2
string
Payment method used for the transaction. Required when creating new transactions, optional for updates. Each method may have different processing times, fees,…
NewTransactionRequestMethod_2
string
Payment method used for the transaction. Required when creating new transactions, optional for updates. Each method may have different processing times, fees,…
UpdateTransactionRequest_2
object
Transaction data to update, referenced by 'txid'. The 'timestamp' field represents the update time. Only the fields to be updated need to be included.
12 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cable-transactions-api-openapi.yml Raw ↑

Other APIs Cable publishes across the network.

Cable alerts API
Cable authentication API
Cable business API
Cable checks API
Cable company API
Cable customerSar API
Cable helper API
Cable identityVerification API
Cable onboardingFlow API
Cable person API
Cable retail API
Cable riskAssessment API
Where this information came from

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