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

Wingspan Wingspan Wallet API

Operations related to Wingspan Wallet

Wingspan Wingspan Wallet API is one of 15 APIs that Wingspan publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Wingspan Wallet. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 3 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0-oas3.1.

Requests are made against 2 base URLs: https://api.wingspan.app, https://stagingapi.wingspan.app.

7 operations 3 paths 9 schemas 1 DELETE2 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0-oas3.1
Base URL
https://api.wingspan.app
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Wingspan Wingspan Wallet API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 7

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

Wingspan Wallet 7

Operations related to Wingspan Wallet

GET
/payments/banking/card
List All Stored Wingspan Wallet Cards
listStoredWingspanWalletCards → 200
POST
/payments/banking/card
Register a New Wingspan Wallet Card
createStoredWingspanWalletCard body → 200
GET
/payments/banking/card/{id}
Retrieve card details by its unique ID
getStoredWingspanWalletCard 1 param → 200
PATCH
/payments/banking/card/{id}
Modify card details by its unique ID
updateStoredWingspanWalletCard 1 param body → 200
DELETE
/payments/banking/card/{id}
Remove a card using its unique ID
deleteStoredWingspanWalletCard 1 param → 200
POST
/payments/banking/card/{id}/token
Request a verification code for card authentication
requestCardAuthentication 1 param body → 200
PATCH
/payments/banking/card/{id}/token
Validate verification code to receive a token
validateReceiveToken 1 param body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are CardDetails (9 properties), Card (6 properties), Address (5 properties), CardCreateRequest (2 properties). Each schema is shown below with its type and property counts.

CardUpdateRequest
object
1 property 1 required
CardCodeRequest
object
1 property 1 required
CardDetails
object
9 properties 9 required
CardTokenRequest
object
2 properties 2 required
CardCodeResponse
object
2 properties 2 required
Card
object
6 properties 7 required
CardTokenResponse
object
2 properties 2 required
CardCreateRequest
object
2 properties
Address
object
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wingspan-wingspan-wallet-api-openapi.yml Raw ↑

Other APIs Wingspan publishes across the network.

Wingspan 1099 Operations API
Wingspan Banking Management API
Wingspan Bulk Operations API
Wingspan Client Management API
Wingspan Collaborator Management API
Wingspan Custom Field Management API
Wingspan Deprecated API
Wingspan Document Signing and Eligibility API
Wingspan Invoice Management API
Wingspan Merchant Category Codes API
Wingspan Payables Management API
Wingspan Payroll Settings API
Where this information came from

This is an independent, third-party profile of Wingspan Wingspan Wallet 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.