---
title: "List card status history"
method: GET
path: "/wallet/v1/cards/{cardId}/status-history"
tags: ["Card status"]
---

# List card status history

`GET /wallet/v1/cards/{cardId}/status-history`

Gets a list of a card's status history. The IDs of the card's account and org/tenant are parsed from the access token.

**Note**: 

  * Only cards with status changes after September/2022 are returned.

  * This endpoint takes an account token - an access token encoded with a Pismo account ID.

For more information, refer to [Card lifecycle and statuses](https://developers.pismo.io/pismo-docs/docs/card-lifecycle-and-statuses).

## Path parameters

- `cardId` string, required

## Query parameters

- `page` string
- `perPage` string

## Headers

- `x-customer-id` integer, required

## Response `200`

Array of card statuses.

- CardStatusListResponse — Card status list response object
  - `items` object[]
    - `status` 'ACTIVE' | 'SUSPENDED' | 'PENDING' — Card status
    - `previous_status` string — Previous card status. Refer to the [Card lifecycle and statuses](https://developers.pismo.io/pismo-docs/docs/card-lifecycle-and-statuses) guide for more information and a complete list.
    - `event_datetime` string — Date/time card status changed, formatted as a RFC3339 string
    - `operation` 'ACTIVATE' | 'UPDATE_STATUS_PUT' | 'UPDATE_STATUS_PATCH' | 'REISSUE' | 'RESET_PASSWORD_TRIES' | 'BIND_NONAME' | 'BIND_REISSUE' | 'TEMPORARY_CARD_INOPERATIVE_EVENT' | 'TEMPORARY_CARD_RENEWAL_EVENT' | 'AUTH_PASSWORD_TRIES_EXCEEDED' | 'AUTHONUS_PASSWORD_TRIES_EXCEEDED' | 'INCREASE_PASSWORD_TRIES_EXCEEDED' | 'MIGRATION' | 'AUTH_REFERRED' — Operation that changed the card status: * `ACTIVATE`—When the card is activated via the [Activate physical card](https://developers.pismo.io/pismo-docs/reference/put-v1-card-activate) endpoint. * `UPDATE_STATUS_PUT`—When the card has its status changed via the [Update card status](https://developers.pismo.io/pismo-docs/reference/put-v1-card-status) endpoint. * `UPDATE_STATUS_PATCH`—When any card data changed via the end [Update card information](https://developers.pismo.io/pismo-docs/reference/patch-v2-card) endpoint. * `REISSUE`—When a card is reissued via the [Reissue card](https://developers.pismo.io/pismo-docs/reference/post-v1-card-reissue) endpoint. * `RESET_PASSWORD_TRIES`—When the password try counter is reset via the [Reset password try count](https://developers.pismo.io/pismo-docs/reference/post-v2-card-password-reset) endpoint. * `BIND_NONAME`—When the card noname and the cardholder are bound via the [Associate noname card with customer](https://developers.pismo.io/pismo-docs/reference/post-v2-card-bind) endpoint. * `BIND_REISSUE`—When the card noname and the holder are bound with reissue use case via the [Associate noname card with customer](https://developers.pismo.io/pismo-docs/reference/post-v2-card-bind) * `TEMPORARY_CARD_INOPERATIVE_EVENT`—When the `TEMPORARY` card is renewed and has its status changed to `NORMAL`. More details about `TEMPORARY` cards at [Cards management](https://developers.pismo.io/pismo-docs/docs/cards-overview-1) * `TEMPORARY_CARD_RENEWAL_EVENT`—When the `TEMPORARY` card is renewed and has its status changed to `INOPERATIVE`. More details about `TEMPORARY` cards at [Cards management](https://developers.pismo.io/pismo-docs/docs/cards-overview-1) * `AUTH_PASSWORD_TRIES_EXCEEDED`—When at the time network authorization (OffUs), the number of password tries made reaches the allowed try limit. * `AUTHONUS_PASSWORD_TRIES_EXCEEDED`—When at the time authorization (OnUs), the number of password tries made reaches the allowed try limit. * `INCREASE_PASSWORD_TRIES_EXCEEDED`—When the number of attempts is increased through the endpoint * `MIGRATION`—When in the card migration flow to Pismo the card status changes. * `AUTH_REFERRED`—When at the time authorization and performing fraud analysis, the issuer can return a flag so that the card is blocked
  - `currentPage` integer — Current page
  - `perPage` integer — Items per page
  - `totalItems` integer — Total items
  - `pages` integer — Total number of pages

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `404` — Not Found
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)