---
title: "Get application"
method: GET
path: "/v1/application/{id}"
tags: ["Get application"]
---

# Get application

`GET /v1/application/{id}`

This operation will respond with an application

## Path parameters

- `id` string, biginteger, required

## Query parameters

- `auditUser` string, required

## Response `200`

Successful lookup of the application

- GetApplication
  - `applicationName` string — Name of the application displayed on the POS terminal in text
  - `enabled` boolean — Allows to define if an application (PAN) is active on the chip. Only active applications are displayed
  - `additionalValues` KeyValuePair[] — The additionalValues array is used to store information in the form of key-value pairs. Enfuce does not perform any validation on these key-value pairs beyond ensuring they adhere to the character limit constraints. The primary purpose of these key-value pairs is to store data without further processing. In newer versions of the card personalization files, these key-value pairs are included in the file. However, this inclusion is version-dependent. We recommend consulting the specific version details of your card personalization files to confirm whether these values will be added to the card personalization file in your case.
    - `key` string, required
    - `value` string, required
  - `printed` boolean — To indicate if this PAN is printed on the physical card
  - `contactPriorityLevel` integer — Priority level of the application (PAN) on a POS terminal (Lowest is the first application listed)
  - `contactlessPriorityLevel` integer — Priority level of the contactless application (PAN) (not visible on terminal). Application with the lowest value will be used for contactless purchases
  - `digitalLayoutCode` string — Id used for digital wallet artwork and other related assets. Use of this need to be agreed with Enfuce separately
  - `accountId` string — The account id card is linked to
  - `id` string — Unique transaction id
  - `maskedCardNumber` string — Card number, masked in order to protect sensitive data
  - `productCode` string — This field is used when the institution has multiple card products setup. The productCode is used to determine the specific card product. Use of this field as well as the values of the field, is dependent on institution setup and should be aligned with Enfuce prior to use.
  - `referenceNumber` string — Unique card identifier for given card
  - `regionAndEcommBlocking` RegionAndEcommBlocking — Card ecomm and geo-region blocking
    - `ecomm` boolean — Block e-comm usage
    - `africa` boolean — Block Africa region
    - `asia` boolean — Block Asia region
    - `europe` boolean — Block Europe region
    - `home` boolean — Block home region
    - `northAmerica` boolean — Block North-America region
    - `oceania` boolean — Block Oceania region
    - `southAmerica` boolean — Block South-America region
  - `cardUsageBlocks` CardUsageBlocks — Card usage blocks
    - `cardPresent` boolean — Card-present environment transactions. true = the transaction type is blocked false = the transaction type is allowed
    - `atmCashDisbursement` boolean — ATM cash disbursement transactions. true = the transaction type is blocked false = the transaction type is allowed
  - `status` 'CARD_OK' | 'CARD_BLOCKED' | 'SUSPECTED_FRAUD' | 'CARD_CLOSED_DUE_TO_FRAUD' | 'CARD_NO_RENEWAL' | 'CARD_LOST' | 'CARD_STOLEN' | 'CARD_CLOSED' | 'CARD_EXPIRED' — - CARD_OK - Card is open and in normal status. Card has to be in this status in order for it to be renewed - CARD_BLOCKED - Temporary block on the card that will prevent approval of authorisations. Can be used instead of account level temporary block if target is to block only a specific card - SUSPECTED_FRAUD - Temporary block on the card that will prevent approval of authorisations. Functionality the same as for "Card blocked", the different code allows to differentiate between the blocks - CARD_CLOSED_DUE_TO_FRAUD - Used to close a card due to known fraud - CARD_NO_RENEWAL - Status set to prevent following card renewal. Does not affect card functionality in any way, only renewal - CARD_LOST - Used to close a card because it is lost - CARD_STOLEN - Used to close a card because it is stolen - CARD_CLOSED - Used to close card by request from customer or bank, reason for closure is set with status update reason. Allows still clearing transaction posting - CARD_EXPIRED - Final card closure status, that blocks also clearing transaction posting
  - `statusDate` string, date-time — Last updated on
  - `usageLimits` GetUsageLimit[] — Usage limits
    - `code` '24H' | 'DAILY' | 'MONTHLY' | 'WEEKLY' | 'ANNUAL_YEARLY' | 'ROLLING_YEARLY' — Usage Limiter Time Periods Available usage limiters include: * __24H__ - A sliding window limiter covering the last 24 hours. * __WEEKLY__ - Limits usage for the current week, starting on Monday. * __MONTHLY__ - Limits usage for the current month, starting on the 1st. __Note:__ The following usage limiters are not part of the standard usage limiter setup. The use of these fields and their values depends on the institution's configuration and must be coordinated with Enfuce before use. * __DAILY__ - Limits usage for the current day, starting at 00:00. * __ANNUAL_YEARLY__ - Limits usage for the current year, starting on 1st January. * __ROLLING_YEARLY__ - A sliding window limiter covering the year until now. (DAILY, WEEKLY, MONTHLY and ANNUAL_YEARLY are reset at midnight UTC)
    - `values` GetLimitValues[]
      - `code` 'ATM' | 'RETAIL' | 'ALL' — Note that all values must be present when set. Usage limiter values are: * __ATM__ - ATM max withdrawal limit * __RETAIL__ - Retail max purchase limit * __ALL__ - All usage max limit
      - `reset` boolean — If set to true this specific usage limit will be reset to product default and any other values sent in to the request will be ignored. Example: If __usageLimits.values.reset__ = true then all values below will be ignored and the default configuration will apply. usageLimits.values.singleAmount = 1000 usageLimits.values.sumAmount = 1200 usageLimits.values.count = 5
      - `singleAmount` number — The max allowed amount of a single transaction. Example: Maximum allowed spend per transaction is 1000 usageLimits.values.singleAmount = 1000 usageLimits.values.sumAmount = 0 usageLimits.values.count = 0
      - `count` integer — The max number of transactions allowed under a time period. Example: Maximum number of allowed transactions under a certain period of time is 5 usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 0 usageLimits.values.count = 5
      - `sumAmount` number — The max allowed amount under a time period. Example: Maximum allowed spend under a certain period of time is 1200. usageLimits.values.singleAmount = 0 usageLimits.values.sumAmount = 1200 usageLimits.values.count = 0
      - `availableAmount` number — Available amount for specific usage limit. Note this is not present if sumAmount is not set.
      - `availableCount` integer — Available count for specific usage limit. Note this is not present if count is not set.
      - `usedAmount` number — Used amount for specific usage limit
      - `usedCount` integer — Used count for specific usage limit

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Application does not exist
- `500` — Internal server error

---

[API](https://skmtc.net/enfuce/apis/transfer-api.md) · [All operations](https://skmtc.net/enfuce/apis/transfer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/enfuce/transfer-api/revisions/dc4a41118f80/schema)