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 Public Profiles API

The Public Profiles API from BanQu — 10 operation(s) for public profiles.

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

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

This API exposes 10 operations across 10 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.

10 operations 10 paths 55 schemas 9 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 Public Profiles 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 10

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

Public Profiles 10
GET
/shared-profile/{ownerId}
Get public profile
1 param → 200404
GET
/shared-profile/{ownerId}/forms
Get forms describing shared profile sections
1 param → 200404
GET
/shared-profile/{ownerId}/related-data-entries
Get data entries related to the profile
5 params → 200
GET
/shared-profile/{ownerId}/geo-data
Get GeoJSON data from related Data Entries and Profile Forms
2 params → 200
GET
/shared-profile/{ownerId}/connections
List public profile connections
4 params → 200404
GET
/shared-profile/{ownerId}/assets
List public profile assets
4 params → 200
GET
/shared-profile/{ownerId}/transactions
List public profile transactions
4 params → 200404
GET
/shared-profile/{ownerId}/transactions/{transactionId}/operations
List public profile transaction operations
2 params → 200404
POST
/shared-profile/{ownerId}/requests
Send profile share request
1 param body → 201403422
GET
/shared-profile/{ownerId}/households
List public profile households. If ownerId is a head of household result contains list of members including himself. If ownerId is dependent result contains all heads of households ownerId is member…
1 param → 200404

Schemas 55

The contract defines 55 schemas that model the data the API accepts and returns. The most detailed are FormField (23 properties), FormFieldWithItems (22 properties), FormDataEntry (17 properties), FragmentField (17 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
ExistentProfile
SharedTransactionStats
object
2 properties
SharedTradeTransaction
object
10 properties 9 required
ProfilePhoto
FormSection
object
14 properties 1 required
ReadWriteVisibility
string
ImmutableId
string
Form
object
12 properties 2 required
FormField
object
23 properties 3 required
FormElementVisibility
Connection
object
1 required
FormGroup
object
5 properties 1 required
SharedTransfer
object
13 properties 12 required
ProfileEmail
SharedBatchTransaction
object
9 properties 9 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
ProfileProperty
object
3 properties 1 required
JsonNestedIdentifier
string
JSON field name, optionally nested, e.g., 'field1.subfield2'
SharedTransaction
FormData
object
Form data that matches parent form schema
LocalizedString
object
1 property 1 required
SharedAsset
object
6 properties 5 required
ShallowProfile
object
6 properties 1 required
SharedAssets
array
List of shared assets
OptionalLocalizedString
object
FormFieldImportance
object
3 properties
SharedTransformationAsset
object
4 properties 3 required
GeoJsonGeometryObject
object
2 properties 2 required
FormMarkupElement
object
8 properties 2 required
ReadWriteHideVisibility
string
SharedTransformationOperation
object
11 properties 10 required
AssetUom
string
ConnectionExtension
object
1 property
FormFieldWithItems
object
22 properties 4 required
Id
string
TransactionParty
object
5 properties
JsonIdentifier
string
JSON field name
FragmentField
object
17 properties 2 required
ProfilePhoneNumber
FormDataEntry
object
Form data entry, assigned by a connected identity or created manually
17 properties
CheckboxField
object
15 properties 2 required
SharedTransformation
object
8 properties 8 required
PhoneNumber
string
Phone Number with Country Prefix
SharedDeposit
object
14 properties 13 required
Resource
object
4 properties
SharedOperations
array
Profile
object
12 properties
Timestamp
number
Number of milliseconds elapsed since January 1, 1970 00:00:00 UTC
SharedTradeOperation
object
14 properties 12 required
AssetCode
string
SharedOperation

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

banqu-public-profiles-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 Public Profiles 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.