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

BackBase Wallet API

The wallet API from BackBase — 2 operation(s) for wallet.

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

This API exposes 12 JSON Schema definitions.

Tagged areas include Wallets. The published artifact set on APIs.io includes an OpenAPI specification and 12 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, /serviceName/client-api/v1.

4 operations 2 paths 12 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.backbase.com
Resource Areas
1

Paths & Operations 4

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

Wallet 4
GET
/wallet/paymentcards
Returns available payment card details for user, optionally filtered by…
getPaymentcards 8 params → 200400406500403415404401
POST
/wallet/paymentcards
Adds a payment card to the user's wallet
postPaymentcards 1 param body → 201400500403415404401
GET
/wallet/paymentcards/{cardId}
Returns details of a specific payment card
getCardIdByCardId 1 param → 200400500403415404401
DELETE
/wallet/paymentcards/{cardId}
Deletes a payment card with a given id
deleteCardIdByCardId 1 param → 204400500403415404401

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are PaymentCard (10 properties), ErrorItem (3 properties), NotFoundError (2 properties), NotAcceptableError (2 properties). Each schema is shown below with its type and property counts.

NotAcceptableError
object
2 properties
UnauthorizedAltError
object
2 properties
ForbiddenError
object
2 properties
UnsupportedMediaTypeError
object
2 properties
InternalServerError
object
Represents HTTP 500 Internal Server Error
1 property 1 required
PaymentCards
array
PaymentCardsPostResponseBody
object
1 property
PaymentCard
object
10 properties 6 required
NotFoundError
object
2 properties
ErrorItem
object
A validation error
3 properties
Currency
object
Schema defining monetary amount in given currency.
2 properties 2 required
BadRequestError
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

backbase-wallet-api-openapi.yml Raw ↑

Other APIs BackBase publishes across the network.

BackBase Approve API
BackBase Bbt API
BackBase Patch API
BackBase Payment Orders API
BackBase Test API
BackBase Utility API
BackBase Validate API
Where this information came from

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