These endpoints cater to fetching, storing, and managing documents related to electronic signatures, including retrieval of signing URLs and saving e-signed documents.
Wingspan Banking Management API is one of 15 APIs that Wingspan publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Banking Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
11 operations
across 8 paths,
and defines 10 schemas.
It is described by OpenAPI 3.1.0, at version 1.0.0-oas3.1.
Requests are made against 2 base URLs: https://api.wingspan.app, https://stagingapi.wingspan.app.
11 operations8 paths10 schemas1 DELETE8 GET1 PATCH1 POST
Metadata
The identity and technical contract details declared by the specification.
Wingspan Banking Management API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
Paths & Operations 11
Across 8 paths, the API surfaces 11 operations — 1 DELETE, 8 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Banking Management 11
These endpoints cater to fetching, storing, and managing documents related to electronic signatures, including retrieval of signing URLs and saving e-signed documents.
GET
/payments/banking/statement
Retrieve All Bank Statements
listBankStatements→ 200
GET
/payments/banking/statement/{id}
Retrieve Specific Bank Statement
getBankStatement1 param→ 200
GET
/payments/banking/statement/{id}/download
Download a specific bank statement as a PDF
downloadBankStatementAsPDF1 param→ 204
GET
/payments/service/banking/{memberId}/application
Fetch the application link for setting up a clearing bank account
getApplicationLink1 param→ 200
GET
/payments/banking/institution/{routingNumber}
Retrieve banking institution details by its routing number
getBankingInstitution1 param→ 200
GET
/payments/payout-settings/{memberId}/debit-card
Fetch all registered payout debit cards for a member
Unlink and delete a specific payout debit card from a member's profile
deleteDebitCard2 params→ 200
GET
/payments/payout-settings/{id}
Retrieve payout settings for a specific member
getPayoutSetting1 param→ 200
PATCH
/payments/payout-settings/{id}
Modify and update payout settings for a specific member
updatePayoutSetting1 parambody→ 200
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are CheckbookCardCreate (6 properties), PayoutDestinationResponse (6 properties), InstitutionResponse (6 properties), CheckbookCard (6 properties). Each schema is shown below with its type and property counts.
PayoutSettingsResponse
object
2 properties2 required
InstitutionResponse
object
6 properties6 required
BankStatement
object
4 properties4 required
PayoutSettingsUpdate
object
2 properties
Address
object
5 properties4 required
PayoutDestinationResponse
object
6 properties5 required
BankingApplicationForm
object
2 properties2 required
PayoutDestinationUpdate
object
4 properties
CheckbookCardCreate
object
6 properties4 required
CheckbookCard
object
6 properties6 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
