Skip to main content
This page provides a comprehensive reference of Core API error codes. You can use this information to diagnose failed transactions and fine-tune your exception-handling capabilities. DiVA API error codes are listed separately. Error codes are based on HTTP response codes: the first three digits specify the HTTP response code, and the last three digits represent the error.
NoteIn contrast to an error code, a transaction response code is a value that is returned by a payment gateway or card issuer to indicate the result of a transaction. This code indicates whether the transaction was approved or declined, as well as why it was declined, if applicable.See the full list of supported transaction response codes in the Transactions guide.

HTTP response codes

The Core API uses standard HTTP response codes to indicate the status of requests:
  • Codes in the 2xx range typically indicate success.
  • Codes in the 4xx range typically indicate an error in the request.
  • Codes in the 5xx range typically indicate an error at the Marqeta platform.
The following table shows some common response codes: If a POST or PUT request causes a validation failure, the Marqeta platform returns a response code of 400 and a body containing details about the exception. For example, a request to associate a card with a non-existent card product returns the following response body:

400001–400099 error codes

400100–400199 error codes

400200–400299 error codes

400300–400399 error codes

400400–400499 error codes

400500–400599 error codes

400600–400699 error codes

400700–400799 error codes

400800–400899 error codes

400900–400999 error codes

401000–401999 error codes

403000–403999 error codes

404000–404999 error codes

405000–405999 error codes

409000–409999 error codes

410000–410999 error codes

412000–412999 error codes

422000–422999 error codes

424000–424999 error codes

429000–429999 error codes

500000–500999 error codes

500100–500199 error codes

500200–500299 error codes

500300–500399 error codes