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

BanQu Asset Transfers API

Asset transfers from one owner to another

BanQu Asset Transfers API is one of 25 APIs that BanQu publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Asset Transfers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 12 operations across 11 paths, and defines 35 schemas. It is described by OpenAPI 3.2.0, at version 3.3.4.

Requests are made against a single base URL, https://banqu.app:443/api/v1.

12 operations 11 paths 35 schemas 6 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.3.4
Base URL
https://banqu.app/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

BanQu Asset Transfers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • Bearer — Your authentication token

Paths & Operations 12

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

Asset Transfers 12

Asset transfers from one owner to another

POST
/assets/{assetId}/transfers
Create assets by asset id transfers
postAssetsByAssetIdTransfers 1 param body → 201400401404
GET
/assets/{assetId}/history
Get assets by asset id history
getAssetsByAssetIdHistory 1 param → 200401404
GET
/assets/{assetId}/holders
Get assets by asset id holders
getAssetsByAssetIdHolders 1 param → 200401404
POST
/assets/{assetId}/holders
Create assets by asset id holders
postAssetsByAssetIdHolders 1 param body → 204400401404
GET
/assets/{assetId}/sources
Get assets by asset id sources
getAssetsByAssetIdSources 7 params → 200400401404
POST
/assets/{assetId}/transfers/batch
Create assets by asset id transfers batch
postAssetsByAssetIdTransfersBatch 1 param body → 200400401404
GET
/transfers
Get transfers
getTransfers 13 params → 200204400401404
GET
/transfers/{transferId}
Get transfers by transfer id
getTransfersByTransferId 1 param → 200400401404
GET
/transfers/{transferId}/sources
Get transfers by transfer id sources
getTransfersByTransferIdSources 6 params → 200400401404
POST
/transfers/{transferId}/confirmReceipt
Create transfers by transfer id confirm receipt
postTransfersByTransferIdConfirmReceipt 1 param body → 204400401404
POST
/transfers/{transferId}/rejectReceipt
Create transfers by transfer id reject receipt
postTransfersByTransferIdRejectReceipt 1 param body → 204400401404
POST
/transfers/{transferId}/resendClaimToken
Create transfers by transfer id resend claim token
postTransfersByTransferIdResendClaimToken 1 param → 204400401404422

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are AssetTransferOperation (42 properties), AssetTransformationOperation (16 properties), AvailableOperationSource (14 properties), AssetDeposit (10 properties). Each schema is shown below with its type and property counts.

ConfirmTransferReceipt
object
2 properties 1 required
PaymentDestinationProvider
string
Payment provider where the payment should be delivered to
PaymentDestinationId
string
Destination phone number for mobile providers; BanQu agency ID for banqu-agency provider
AssetHolder
object
7 properties
AssetDeposit
object
10 properties 8 required
EffectiveLocation
Id
string
Timestamp
number
Number of milliseconds elapsed since January 1, 1970 00:00:00 UTC
NewMultipleTransfer
array
AssetDescription
string
PaymentDestination
AnyAssetOperation
RejectTransferReceipt
object
1 property
AvailableOperationSource
object
Operation that can be reused as a source for another asset transfer
14 properties 5 required
AssetUom
string
ImmutableId
string
PaymentDestinationType
mobile for payments by phone number; payCode for 6DOT50 partner transfer
AssetTransformationOperation
object
Operation that indicates asset(s) transformation into an arbitrary amount of some different asset(s)
16 properties 9 required
SourcesCount
number
Indicates number of operations that serve as explicit or implicit sources for this asset operation. Appears in the object when request contains sourcesGrouping…
ProfileProperty
object
3 properties 1 required
DateTime
string
AssetTransferOperation
object
Movement of some asset amount between two accounts, denoted sender and receiver
42 properties 4 required
GeoCoordinates
object
2 properties 2 required
AssetMobileDestination
object
Mobile wallet where the monetary transfer was sent to
3 properties 2 required
DepositAssetRequest
object
5 properties 2 required
EffectiveDate
AssetCode
string
AssetTransferRequest
object
10 properties 2 required
SourceOperations
array
List of incoming asset transfers that are used as sources for this transaction
AssetAgencyDestination
object
Where the transfer was sent to (i.e. BanQu agency)
3 properties 2 required
Attachment
object
5 properties 1 required
Attachments
array
AssetHistory
array
TransformingAsset
object
4 properties 3 required
ImmutableTimestamp
number
Number of milliseconds elapsed since January 1, 1970 00:00:00 UTC

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

banqu-asset-transfers-api-openapi.yml Raw ↑

Other APIs BanQu publishes across the network.

BanQu Asset Categories API
BanQu Asset Sharing API
BanQu Asset Transactions API
BanQu Asset Transfer Claiming API
BanQu Asset Transformations API
BanQu Assets API
BanQu Attachments API
BanQu Authentication API
BanQu Connections API
BanQu Data Processors API
BanQu Form Data Entries API
BanQu Forms API
Where this information came from

This is an independent, third-party profile of BanQu Asset Transfers 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.