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

Spotnana Personal Payment Sources API

The Personal Payment Sources API from Spotnana — 2 operation(s) for personal payment sources.

Spotnana Personal Payment Sources API is one of 33 APIs that Spotnana publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Personal Payment Sources. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 5 operations across 2 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against a single base URL, https://api-ext-sboxmeta.partners.spotnana.com.

5 operations 2 paths 27 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://apis.spotnana.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Spotnana Personal Payment Sources API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer). By default, every request must be authenticated.

Paths & Operations 5

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

Personal Payment Sources 5
GET
/v2/payment/users/{userId}/payment-sources
List personal payment sources for a User
listUserPaymentSources 3 params → 200400401403
POST
/v2/payment/users/{userId}/payment-sources
Create Personal Payment Source.
createPersonalPaymentSource 1 param body → 200400401403
GET
/v2/payment/users/{userId}/payment-sources/{paymentSourceId}
Fetch a personal payment source
getPersonalPaymentSource 2 params → 200400401403404
DELETE
/v2/payment/users/{userId}/payment-sources/{paymentSourceId}
Delete a Personal Payment Source.
deletePersonalPaymentSource 2 params → 200400401403404
PATCH
/v2/payment/users/{userId}/payment-sources/{paymentSourceId}
Update a Personal Payment Source.
updatePersonalPaymentSource 2 params body → 200400401403404

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are PostalAddress (19 properties), CardV2 (8 properties), PaymentSourceInfoV2 (5 properties), CardUpdate (3 properties). Each schema is shown below with its type and property counts.

CardUpdate
object
Card Details to be updated
3 properties
UsagePaymentFilter
object
Defines usage restrictions or filters for a payment source.
CardV2
object
Card Details
8 properties 6 required
PaymentSourceDetails
object
Contains details about a payment source, including its type and specific attributes.
ErrorResponse
object
2 properties
Latlng
object
Latitude and Longitude for a Location
2 properties 2 required
PersonalPaymentFilter
object
Defines filter specific to personal payment sources.
3 properties 2 required
ManagedTravelerPaymentAccess
object
Settings for sharing this payment method with managed traveler profiles. Applicable for Arranger Roles.
2 properties 1 required
AuthenticationInfo
object
Provides authentication details, such as URLs for 3DS.
1 property
TravelType
string
Travel Type
Expiry
object
Contains the expiry of a Card.
2 properties 2 required
ErrorParameter
object
Error parameter
2 properties
ListPaymentSourceResponse
object
Response containing a list of payment sources along with pagination details.
2 properties
PaymentSourceStatus
string
Status of the Payment Source.
OffsetBasedPaginationResponseParams
object
Pagination parameters for response.
1 property 1 required
PaymentSourceUpdateDetails
object
Specifies the details required to update an existing payment source.
TMCPaymentFilter
object
Defines filter specific to tmc payment sources.
1 property 1 required
PostalAddress
object
Postal Address Details
19 properties 2 required
GetPaymentSourceResponseV2
object
Response returned when fetching details of a payment source.
1 property
UpdatePersonalPaymentSourceRequest
object
Request payload for updating an existing personal payment source.
2 properties 1 required
CardPaymentSource
object
Represents payment source details for a credit card.
2 properties 2 required
PaymentSourceInfoV2
object
5 properties 2 required
CardCompany
string
The issuing company of card
CreatePaymentSourceRequestV2
object
Represents the request payload to create a new payment source.
1 property 1 required
OwnershipLabel
string
Ownership label of the card whether it is personal, corporate or central.
CreatePaymentSourceResponseV2
object
Response returned upon creating a payment source.
3 properties
CardPaymentSourceUpdate
object
This describes the details for a card payment source.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spotnana-personal-payment-sources-api-openapi.yml Raw ↑

Other APIs Spotnana publishes across the network.

Spotnana Air API
Spotnana Air Credits API
Spotnana API User API
Spotnana Approval API
Spotnana Authentication API
Spotnana Autocomplete API
Spotnana Companies API
Spotnana Company Enrollment API
Spotnana Company Policies API
Spotnana Company Tier API
Spotnana Cost Centers API
Spotnana Custom Fields API
Where this information came from

This is an independent, third-party profile of Spotnana Personal Payment Sources 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.