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 Sharing API

The Asset Sharing API from BanQu — 6 operation(s) for asset sharing.

BanQu Asset Sharing 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 Sharing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 8 operations across 6 paths, and defines 55 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.

8 operations 6 paths 55 schemas 1 DELETE6 GET1 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 Sharing 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 8

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

Asset Sharing 8
GET
/assets/shares
List asset shares
→ 200401
POST
/assets/shares
Create asset share
body → 201400401404
GET
/assets/shares/{shareId}
Get asset share details
1 param → 200404
DELETE
/assets/shares/{shareId}
Delete asset share
1 param → 204401404
GET
/assets/shares/{shareId}/transfers
Get shared asset history
7 params → 200404
GET
/assets/shares/{shareId}/transfers/{transferId}
Get shared asset transfer details
2 params → 200404
GET
/assets/shares/{shareId}/transfers/{transferId}/sources
List shared asset transfer sources
6 params → 200404
GET
/assets/shares/{shareId}/transfers/{transferId}/form
Get shared asset transfer properties form
2 params → 200404

Schemas 55

The contract defines 55 schemas that model the data the API accepts and returns. The most detailed are AssetTransferOperation (42 properties), FormField (23 properties), FormFieldWithItems (22 properties), AssetShareTransfer (19 properties). Each schema is shown below with its type and property counts.

AssetMobileDestination
object
Mobile wallet where the monetary transfer was sent to
3 properties 2 required
Attachment
object
5 properties 1 required
AssetDescription
string
GeoCoordinates
object
2 properties 2 required
AssetDeposit
object
10 properties 8 required
PaymentDestinationId
string
Destination phone number for mobile providers; BanQu agency ID for banqu-agency provider
AnyAssetOperation
FormSection
object
14 properties 1 required
ReadWriteVisibility
string
ImmutableId
string
FormGroup
object
5 properties 1 required
Form
object
12 properties 2 required
FormField
object
23 properties 3 required
FormElementVisibility
EffectiveLocation
PaymentDestination
AssetInfo
object
13 properties 7 required
ParentFieldName
string
Name of a parent field whose selected value filters options in this field. E.g., selecting a connection filters related data entries
DescriptionVariant
string
JsonNestedIdentifier
string
JSON field name, optionally nested, e.g., 'field1.subfield2'
AssetTransferShareDetail
object
8 properties
SourceOperations
array
List of incoming asset transfers that are used as sources for this transaction
AssetShareTransfer
object
19 properties
LocalizedString
object
1 property 1 required
ImmutableTimestamp
number
Number of milliseconds elapsed since January 1, 1970 00:00:00 UTC
OptionalLocalizedString
object
TransformingAsset
object
4 properties 3 required
NewAssetShare
object
6 properties 1 required
AssetShareRow
FormFieldImportance
object
3 properties
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…
PaymentDestinationType
mobile for payments by phone number; payCode for 6DOT50 partner transfer
FormMarkupElement
object
8 properties 2 required
AssetHistory
array
Attachments
array
ReadWriteHideVisibility
string
AssetUom
string
FormFieldWithItems
object
22 properties 4 required
Id
string
AssetShareDetail
object
6 properties 4 required
JsonIdentifier
string
JSON field name
AssetTransferShareData
object
8 properties 6 required
EffectiveDate
FragmentField
object
17 properties 2 required
AssetShareList
array
CheckboxField
object
15 properties 2 required
AssetTransformationOperation
object
Operation that indicates asset(s) transformation into an arbitrary amount of some different asset(s)
16 properties 9 required
DateTime
string
AssetShare
AssetTransferOperation
object
Movement of some asset amount between two accounts, denoted sender and receiver
42 properties 4 required
AssetShareData
object
6 properties 4 required
AssetAgencyDestination
object
Where the transfer was sent to (i.e. BanQu agency)
3 properties 2 required
Timestamp
number
Number of milliseconds elapsed since January 1, 1970 00:00:00 UTC
PaymentDestinationProvider
string
Payment provider where the payment should be delivered to
AssetCode
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs BanQu publishes across the network.

BanQu Asset Categories API
BanQu Asset Transactions API
BanQu Asset Transfer Claiming API
BanQu Asset Transfers 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 Sharing 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.