The API Report CardAPI Index
Marqeta

Marqeta API

marqeta.com

Marqeta is API-first: the Core REST API at /v3 is the whole product, with a three-click self-serve sandbox. Production access runs through an MSA with usage-based pricing plus sponsor-bank approval that adds weeks. Rate limits are unpublished and negotiated per contract.

Last verified: October 2026Financial ServicesMCP READY
API GRADE
A
VERIFIED OCT 2026

SCORECARD

ExistenceGOODThe Core REST API at /v3 is the entire product surface: cards, users, transactions, webhooks, plus a separate DiVA reporting API.
AccessMIXEDSandbox signup is self-serve in three clicks, but production requires an MSA and program setup on a customer-specific subdomain.
CoverageGOODCard issuing, users, transactions, KYC, chargeback cases, and digital wallet tokens are all API-reachable; DiVA covers reporting.
AuthGOODHTTP Basic with per-environment application and access tokens; webhooks are HMAC SHA-256 signed for sender verification.
Docs & DXGOODInteractive docs, OpenAPI spec, Postman collections, and a sandbox dashboard; official SDKs are thin, so most generate clients.
StabilityGOODPath-based versioning on a single /v3 line; webhook retries are configurable and delivery is at-least-once.
MCPGOODMarqeta publishes an official MCP server in its GitHub org, distributed on npm as @marqeta/marqeta-mcp with documented setup and 33 tools across cards, users, transactions, and disputes. The repository shows activity in 2026. github.com ↗ VERIFIED 2026-08
MORE FROM THE REPORT CARD
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Marqeta scores A on Supergood's API Report Card. Marqeta is API-first: the Core REST API at /v3 is the whole product, with a three-click self-serve sandbox. Production access runs through an MSA with usage-based pricing plus sponsor-bank approval that adds weeks. Rate limits are unpublished and negotiated per contract.

Tried to integrate with Marqeta?
SOURCES
Limited first-party SDK coverage compared to Stripe, most customers hand-roll HTTP or generate clients, which slows initial integration apitracker.io ↗
Pagination is offset-based rather than cursor-based, which is slower and less reliable at scale and inconsistent with modern fintech APIs marqeta.com ↗
Rate limits are not publicly documented, customers must negotiate limits with the account team and discover ceilings empirically marqeta.com ↗
Sandbox does not perfectly simulate production behaviors, real network behaviors (Visa/Mastercard quirks), real fraud signals, and real authorization-stream timing differ from sandbox simulations marqeta.com ↗
Webhook delivery is at-least-once with retries, handlers must be idempotent to handle redelivery without double-posting transactions to the customer ledger marqeta.com ↗
Some resources (cardholders, KYC) require sponsor-bank approval flows that cannot be exercised end-to-end in sandbox marqeta.com ↗
Public-sandbox program tokens are shared with other developers, so test data is visible and noisy; private sandbox is required for serious dev work marqeta.com ↗
OpenAPI/Swagger spec is published but is not always kept in lockstep with the live API, beta endpoints may be missing marqeta.com ↗
Versioning is by URL path (`/v3`) only, there is no date-stamped header versioning, so breaking changes within v3 are managed via release notes and customer comms rather than per-account pinning marqeta.com ↗
Authorization-decisioning webhooks (the JIT Funding hot path) have tight latency budgets, customers must respond in well under a second or transactions decline, which forces them to host edge infrastructure marqeta.com ↗
Onboarding to production requires a full bank-sponsor due-diligence package (BSA/AML, KYC policy, capitalization, etc.) that the API alone cannot exercise marqeta.com ↗
Heavy revenue concentration with Block/Cash App (45% of revenue in 2024 down from 68%) has historically driven price compression on renewals and made other customers worry about strategic prioritization investordesk.com.au ↗
Sponsor-bank gating: customers must still get approved by Marqeta's underlying sponsor banks (Sutton, Pathward, Evolve, etc.), which adds weeks-to-months to onboarding despite the 'live in days' marketing marqeta.com ↗
Pandemic-era growth slowed sharply post-2022 as on-demand TPV normalized; Marqeta has had to renegotiate with anchor customers at lower take rates americanbanker.com ↗
Sandbox/onboarding UX has been called out in public design critiques for outdated form fields, premature error states, and WCAG accessibility gaps ethanchng.com ↗
Credit issuing capability (vs. debit/prepaid) launched late and lagged Galileo and Stripe Issuing in coverage and feature parity americanbanker.com ↗
Revenue-share economics shift unfavorably for smaller programs that never hit the volume tiers that unlock better interchange splits fourweekmba.com ↗
Competing against Stripe Issuing is hard for new customers already on Stripe payments, bundling pressure is significant g2.com ↗
Implementation/professional-services attach is significant, customers report needing Marqeta's Delivery team for non-trivial card programs, lengthening time-to-launch marqeta.com ↗
International expansion (EMEA, APAC) has been slower than competitors like Paymentology, Wallester and Thredd in those regions dashdevs.com ↗
Public-market scrutiny since 2021 IPO has driven stock volatility and management churn (CEO transition 2023), affecting customer perception of stability americanbanker.com ↗