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

The User Profile Sharing API from BanQu — 11 operation(s) for user profile sharing.

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

This API exposes 16 operations across 11 paths, and defines 41 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.

16 operations 11 paths 41 schemas 2 DELETE10 GET1 PATCH3 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 User Profile 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 16

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

User Profile Sharing 16
GET
/profile/sharing
Get profile sharing settings
→ 200401
PATCH
/profile/sharing
Change profile sharing settings
body → 200400401
GET
/profile-shared-packages
List packaged profile shares
→ 200401
POST
/profile-shared-packages
Create packaged profile share
body → 201401
GET
/profile-shared-packages/{id}
Get packaged profile share details
1 param → 200
DELETE
/profile-shared-packages/{id}
Delete packaged profile share
1 param → 204
GET
/profile-shared-packages/{id}/assets
List packaged profile share assets
4 params → 200401
GET
/profile-shared-packages/{id}/transactions
List packaged profile share transactions
1 param → 200401
GET
/profile-shared-packages/{id}/connections
List packaged profile share connections
1 param → 200401
GET
/profile-shared-packages/{id}/asset-categories
List packaged profile share categories
1 param → 200401
GET
/profile-shared-packages/{id}/geo-data
Get GeoJSON data from shared Profile Sections
1 param → 200
GET
/profile/shares
List profile shares
→ 200
POST
/profile/shares
Create profile share
body → 201403422
GET
/profile/shares/{otherPartyId}
Get profile share request details
1 param → 200403404
DELETE
/profile/shares/{otherPartyId}
Delete/reject profile share request
1 param → 204403404
POST
/profile/shares/{senderId}/approve
Accept profile share request
1 param body → 200403404

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are ExchangeTransaction (31 properties), AssetDepositTransaction (16 properties), Profile (12 properties), ProfileShareRequests (8 properties). Each schema is shown below with its type and property counts.

GeoJsonFeatureCollection
object
2 properties 2 required
Attachment
object
5 properties 1 required
AssetDescription
string
GeoCoordinates
object
2 properties 2 required
PaymentDestinationId
string
Destination phone number for mobile providers; BanQu agency ID for banqu-agency provider
ProfilePhoto
ProfileShareRequests
object
User profile data
8 properties
ImmutableId
string
EffectiveLocation
Connection
object
1 required
PackagedShareProfile
object
6 properties
ProfileEmail
Transaction
AssetTransformationTransaction
object
Asset Transformation
8 properties 6 required
ShareRequest
object
A share request
4 properties
NewPackagedShareProfile
object
3 properties
RevertTransaction
object
3 properties 1 required
ProfileProperty
object
3 properties 1 required
SharedAsset
object
6 properties 5 required
SharedAssets
array
List of shared assets
TransformingAsset
object
4 properties 3 required
PaymentDestinationType
mobile for payments by phone number; payCode for 6DOT50 partner transfer
GeoJsonGeometryObject
object
2 properties 2 required
ProfileVisibility
object
4 properties 4 required
Attachments
array
AssetUom
string
ConnectionExtension
object
1 property
Id
string
ExchangeTransaction
object
31 properties 2 required
TransactionParty
object
5 properties
PackagedShareProfileListItem
object
Packaged share profile data
8 properties
EffectiveDate
AssetCode
string
ProfilePhoneNumber
DateTime
string
PhoneNumber
string
Phone Number with Country Prefix
AssetDepositTransaction
object
16 properties 14 required
Resource
object
4 properties
Profile
object
12 properties
PaymentDestinationProvider
string
Payment provider where the payment should be delivered to
AssetCategory
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

banqu-user-profile-sharing-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 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
Where this information came from

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