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

Moov Card Issuing API

Virtual spending cards, authorizations, and card transactions.

Moov Card Issuing API is one of 19 APIs that Moov publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Card Issuing. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 8 paths. It is described by OpenAPI 3.2.0, at version v2026.04.00.

Requests are made against a single base URL, https://api.moov.io.

10 operations 8 paths 0 schemas 8 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2026.04.00
Server
https://api.moov.io
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Moov Card Issuing API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 access token passed as a Bearer token.

Paths & Operations 10

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

Card Issuing 10

Virtual spending cards, authorizations, and card transactions.

POST
/issuing/{accountID}/cards
Create a spending card.
createIssuedCard 1 param → 200
GET
/issuing/{accountID}/cards
List spending cards.
listIssuedCards 1 param → 200
GET
/issuing/{accountID}/cards/{issuedCardID}
Retrieve a spending card.
getIssuedCard 2 params → 200
PATCH
/issuing/{accountID}/cards/{issuedCardID}
Update a spending card.
updateIssuedCard 2 params → 200
GET
/issuing/{accountID}/cards/{issuedCardID}/details
Get PCI details for a spending card.
getIssuedCardDetails 2 params → 200
GET
/issuing/{accountID}/authorizations
List authorizations.
listAuthorizations 1 param → 200
GET
/issuing/{accountID}/authorizations/{authorizationID}
Retrieve an authorization.
getAuthorization 2 params → 200
GET
/issuing/{accountID}/authorizations/{authorizationID}/events
List authorization events.
listAuthorizationEvents 2 params → 200
GET
/issuing/{accountID}/card-transactions
List card transactions.
listCardTransactions 1 param → 200
GET
/issuing/{accountID}/card-transactions/{cardTransactionID}
Retrieve a card transaction.
getCardTransaction 2 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

moov-card-issuing-api-openapi.yml Raw ↑

Other APIs Moov publishes across the network.

Moov Drops
Moov Backend SDKs
Moov Accounts API
Moov Authentication API
Moov Bank Accounts API
Moov Capabilities API
Moov Cards API
Moov Disputes API
Moov Payment Links API
Moov Payment Methods API
Moov Refunds API
Where this information came from

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