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

Sponge Cards API

The Cards API from Sponge — 6 operation(s) for cards.

Sponge Cards API is one of 10 APIs that Sponge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 7 operations across 6 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.wallet.paysponge.com.

7 operations 6 paths 11 schemas 1 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.wallet.paysponge.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Sponge Cards API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API Key) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 7

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

Cards 7
POST
/api/credit-cards
Store a credit card
postApiCreditCards body → 200
GET
/api/credit-cards
List stored credit card payment methods
getApiCreditCards 1 param → 200
POST
/api/agents/{id}/link-payment-methods/link
Connect or save a Link payment method
postApiAgentsIdLinkPaymentMethodsLink 1 param body → 200
POST
/api/agents/{id}/link-payment-methods/credential
Create a Link payment credential
postApiAgentsIdLinkPaymentMethodsCredential 1 param body → 200
POST
/api/cards
Get a checkout card
postApiCards body → 200
POST
/api/virtual-cards
Issue a virtual card
postApiVirtualCards body → 200
POST
/api/card-usage
Report card usage
postApiCardUsage body → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are StoreCreditCardRequest (12 properties), IssueVirtualCardRequest (10 properties), ReportCardUsageRequest (8 properties), CardShippingAddress (7 properties). Each schema is shown below with its type and property counts.

LinkPaymentMethodRequest
object
7 properties
LinkPaymentCredentialRequest
object
7 properties
CardBillingAddress
object
6 properties 5 required
ReportCardUsageRequest
object
8 properties 2 required
StoreCreditCardRequest
object
12 properties 6 required
ProductLineItem
object
3 properties 3 required
GetCardRequest
object
7 properties
VirtualCardShippingAddress
object
5 properties 5 required
LinkAddress
object
7 properties 6 required
CardShippingAddress
object
7 properties 6 required
IssueVirtualCardRequest
object
10 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sponge-cards-api-openapi.yml Raw ↑

Other APIs Sponge publishes across the network.

Sponge Agents API
Sponge Fiat API
Sponge MPP API
Sponge Payments API
Sponge Secrets API
Sponge Sponge Card API
Sponge Trading API
Sponge Transfers API
Sponge Wallet API
Where this information came from

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