> For the complete documentation index, see [llms.txt](https://customer-api-docs.ibanera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://customer-api-docs.ibanera.com/api-endpoints/cards/get-card-details-by-id.md).

# Get Card Details By ID

## Get Card Details By ID

**Description**: This endpoint allows you to retrieve detailed information about a specific card using its unique identifier. It's particularly useful for accessing card attributes such as balance, expiry date, and associated account details.

**Endpoint:** `/api/v1/customer/cards/carddetails`   

**Request Method**: Get

**Headers**:

* `Content-Type: application/json`
* `Authorization: Bearer <token>`
* `otp: 1234`

**Request Query Parameters**:

* `CardId` (integer, required): The unique identifier for the top-up card whose details are being requested.

#### **Response Body Example (200 OK)**:

* ```json
  {
      "id": 0,
      "details": {
          "customersID": 0,
          "customersReference": "string",
          "cardHolderName": "string",
          "cardLast4": "string",
          "currency": "string",
          "totalBalance": 0,
          "availableBalance": 0,
          "status": "string"
      },
      "status": "1",
      "errors": []
  }
  ```

  **Errors**:

  * `404 Not Found`: Returned if the card ID does not exist.
  * `401 Unauthorized`: If the request does not include valid authentication.

***

## **Get Sensitive Card Details By ID**

**Description**: This endpoint allows you to retrieve sensitive information about a specific card using its unique identifier. It's particularly useful for accessing card attributes such as card number, bank details, and cvc.

**Endpoint:** `/api/v1/customer/cards/sensitive-details`

**Request Method**: Get

**Headers**:

* `Content-Type: application/json`
* `Authorization: Bearer <token>`
* `otp: 1234`

**Request Query Parameters**:

* `CardId` (integer, required): The unique identifier for the top-up card whose details are being requested.

**Response Body Example (200 OK)**:

* ```json
  {
    "id": 0,
    "details": {
      "cardHolderName": "string",
      "expiryDate": "2025-12-05T18:28:08.228Z",
      "cardNumber": "string",
      "cvc": "string",
      "currency": "string",
      "totalBalance": 0,
      "availableBalance": 0,
      "status": "string",
      "orderStatus": "string",
      "processorCardStatus": "string",
      "pin": "string",
      "accounts": [
        {
          "id": 0,
          "accountNumber": "string",
          "routingNumber": "string",
          "bankName": "string",
          "bankAddress": "string",
          "accountHolderName": "string",
          "accountHolderAddress": "string"
        }
      ]
    },
    "status": "string",
    "errors": [
      {
        "fieldName": "string",
        "messageCode": "string"
      }
    ]
  }
  ```

  **Errors**:

  * `404 Not Found`: Returned if the card ID does not exist.
  * `401 Unauthorized`: If the request does not include valid authentication.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://customer-api-docs.ibanera.com/api-endpoints/cards/get-card-details-by-id.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.