---
agentTools:
  projectIndex: https://partner.getpliant.com/llms.txt
---

# Detailed card status

> 🚧 Breaking change `2.0.0` -› `2.1.0`

We are introducing **more granular card status information** which helps you e.g identifying if the card has been locked by the user deliberately or because the PIN was entered incorrectly more than 3 times.

## Granular card status

The following endpoints are modified

* [GET /cards](https://partner.getpliant.com/v2.1.0/reference/getorganizations-1) (query & response parameter)
* [GET /cards/\{cardId}](https://partner.getpliant.com/v2.1.0/reference/getorganizations-1) (response parameter)
* [POST /cards/details](https://partner.getpliant.com/v2.1.0/reference/getorganizations-1) (response parameter)
* [POST /cards/subscription](https://partner.getpliant.com/reference/createcardsubscription-1) (new event `CARD_STATUS_UPDATED` with callback payload `cardStatusUpdated`)

The allowed ENUM values for the new property `detailedStatus` are listed below:

```Text detailedStatus
PENDING_ACTIVATION
PENDING_ISSUANCE
PENDING_REGISTRATION
REQUEST_APPROVED
REQUESTED
REQUEST_CANCELLED
REQUEST_REJECTED
ACTIVE
LOCKED
LOCKED_PIN
EXPIRED
TERMINATED
TERMINATED_LOST
TERMINATED_STOLEN
```

> 📘 This change is only available in API Version `2.1.0`

## Minor changes

* We added the `type` property as a query parameter and to the response of the [GET /cards](https://partner.getpliant.com/reference/getcards-1) endpoint.
* With version `2.1.0` we are removing endpoints related to the Bills entity (details see [https://partner.getpliant.com/changelog/statements-booking-datethis changelog article]()) completely from our API.