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

Lightspark Cards API

Card management endpoints. Issue debit cards against an internal account, freeze / unfreeze, close, manage card funding sources, and list card transactions.

Lightspark Cards API is one of 22 APIs that Lightspark 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, API documentation, and an API reference.

This API exposes 5 operations across 3 paths, and defines 17 schemas. It is described by OpenAPI 3.1.0, at version 2025-10-13.

Requests are made against a single base URL, https://api.lightspark.com/grid/2025-10-13.

5 operations 3 paths 17 schemas 2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2025-10-13
Base URL
https://api.lightspark.com/grid/2025-10-13
Authentication
HTTP Basic, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Lightspark Cards API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuth). It accepts HTTP bearer tokens (AgentAuth). An API key is passed in the header as X-Grid-Signature (WebhookSignature). By default, every request must be authenticated.

  • BasicAuth — API token authentication using format :
  • AgentAuth — Bearer token authentication for agent-scoped endpoints. The token is the accessToken returned when redeeming a device code via POST /agents/device-codes/{code}…
  • WebhookSignature — Secp256r1 (P-256) asymmetric signature of the webhook payload, which can be used to verify that the webhook was sent by Grid. To verify the signature: 1. Get t…

Paths & Operations 5

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

Cards 5

Card management endpoints. Issue debit cards against an internal account, freeze / unfreeze, close, manage card funding sources, and list card transactions.

POST
/cards
Issue a card
createCard body → 201400401500501
GET
/cards
List cards
listCards 7 params → 200400401500501
GET
/cards/{id}
Get a card
getCardById 1 param → 200401404500501
PATCH
/cards/{id}
Update a card
updateCardById 3 params body → 200202400401404409500501
POST
/cards/{id}/reveal
Reveal card details
revealCard 1 param → 200401403404500501

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are Card (16 properties), Error500 (4 properties), CardListResponse (4 properties), Error409 (4 properties). Each schema is shown below with its type and property counts.

SignedRequestChallenge
object
Common base for two-step signed-retry challenge responses on Embedded Wallet endpoints (credential registration or revocation, session refresh or revocation, w…
3 properties 3 required
Error501
object
4 properties 3 required
CardBrand
string
Card network brand. Read-only — determined by Grid when the card is provisioned with the issuer.
Error403
object
4 properties 3 required
Error400
object
4 properties 3 required
Error409
object
4 properties 3 required
CardRevealResponse
object
2 properties 2 required
CardState
string
Lifecycle state of a card. | State | Description | |-------|-------------| | PENDINGKYC | The cardholder has not yet completed KYC. Cards in this state cannot…
CardListResponse
object
4 properties 2 required
CardUpdateRequest
object
Update request for PATCH /cards/{id}. At least one of state or fundingSources must be supplied. state transitions are limited to ACTIVE ⇄ FROZEN and ACTIVE | F…
2 properties
CardStateReason
string
Reason a card reached a terminal or non-active state. Present on CLOSED cards, and on cards that fail provisioning before reaching ACTIVE. | Reason | Descripti…
Error500
object
4 properties 3 required
CardForm
string
Physical form factor of the card. Only VIRTUAL is supported in v1; PHYSICAL will be added in a later release.
Card
object
16 properties 7 required
CardCreateRequest
object
4 properties 3 required
Error401
object
4 properties 3 required
Error404
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lightspark-cards-api-openapi.yml Raw ↑

Other APIs Lightspark publishes across the network.

Lightspark Agent Management API
Lightspark Agent Operations API
Lightspark API Tokens API
Lightspark Available UMA Providers API
Lightspark Contact Verification API
Lightspark Cross-Currency Transfers API
Lightspark Customers API
Lightspark Discoveries API
Lightspark Documents API
Lightspark Embedded Wallet Auth API
Lightspark Exchange Rates API
Lightspark External Accounts API
Where this information came from

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