Nestcoin ledger-transfer API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as x-signature (authSignature).
An API key is passed in the header as x-auth-token (authToken).
authToken — Auth Token header for inter-service communication
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are AccountTransaction (14 properties), InternalTransfer (10 properties), TransactionBlockchainInfo (8 properties), InternalTransferRequest (5 properties). Each schema is shown below with its type and property counts.
ErrorMessageDto
object
Default error object for services. This gives consistent error object that all services may use.
3 properties2 required
AccountTransaction
object
14 properties7 required
InternalTransferRequest
object
Internal request to transfer funds between two sub-accounts of between main account and sub-account. The accounts must have the same currency.
5 properties3 required
TransactionType
string
TransactionStatus
string
Status of the transaction, indicating its current state in the processing lifecycle. - PENDING: The transaction has been created but not yet processed. - INPRO…
TransactionBlockchainInfo
object
Blockchain transaction data, present on Crypto-backed transactions.
8 properties4 required
User2FAMethod
string
TransferResponse
object
The payment initiation response
4 properties3 required
TransactionBlockchainAddress
object
Address data
2 properties1 required
CryptoTransferDestination
object
The destination details of the transfer. Either beneficiaryId or address must be provided.
4 properties1 required
CryptoTransferRequest
object
Request object for crypto payment initiation request. The sourceAccountId can be a main account or sub-account.
4 properties3 required
InternalTransfer
object
10 properties7 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
