> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/configuration/system-status-information-property-group-2.3.1.nnn/system-status-injected-key-information-property-subgroup-2.3.1.1.1.n.md).

# System Status Injected Key Information - Property Subgroup 2.3.1.1.1.n

## Table SSIK-1 - Device Key Status - Property 2.3.1.1.1.1&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>2.3.1.1.1.1 / 0x020301010101</td></tr><tr><td valign="top">Name</td><td>Device Key Status</td></tr><tr><td valign="top">Description</td><td>This OID contains a 32-bit bitmap. Each bit indicates the status of a device key. A bit value of 1 indicates the corresponding key has been injected.</td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>4</td></tr><tr><td valign="top">Max. Len (b)</td><td>4</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top"><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p> </p><p>Valid Values</p></td><td><p>Bit 0:    TMPTK_1000</p><p>Bit 1:    MTK_1001</p><p>Bit 2:    DEVTK_1002</p><p>Bit 3:    FINTK_1003</p><p>Bit 4:    PRODTK_1021</p><p>Bit 5:    MFGTK_1022</p><p>Bit 6:    MFIFTK_1081</p><p>Bit 7:    AKIFTK_1091</p><p>Bit 8:    FREQMK_1101</p><p>Bit 9:    MREQMK_1102</p><p>Bit 10: MFRQMK_1111</p><p>Bit 11: ARQ1MK_1121</p><p>Bit 12: ARQ2MK_1122</p><p>Bit 13 – 31: Reserved</p></td></tr><tr><td valign="top">Default</td><td>None</td></tr></tbody></table>

## Table SSIK-2 - Device Key Status - Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 8104010ED101 841AD101 81072B06010401F609 850102 890AE308E106E104E102C100</td></tr></tbody></table>

## Table SSIK-3 - Device Key Status - Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 8104820ED101 820400000000 8482001E D101 81072B06010401F609 850102 890EE30CE10AE108E106C1040000077E</td></tr></tbody></table>

## Table SSIK-4 - Transaction Key Status - Property 2.3.1.1.1.2&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Property Description</td><td></td></tr><tr><td valign="top">Property OID</td><td>2.3.1.1.1.2 / 0x020301010102</td></tr><tr><td valign="top">Name</td><td>Transaction Key Status</td></tr><tr><td valign="top">Description</td><td>This OID contains a 32-bit bitmap. Each bit indicates the status of a transaction key. A bit value of 1 indicates the corresponding key has been injected.</td></tr><tr><td valign="top">Securing Key</td><td>None</td></tr><tr><td valign="top">Min. Len (b)</td><td>4</td></tr><tr><td valign="top">Max. Len (b)</td><td>4</td></tr><tr><td valign="top">Data Type</td><td>Binary</td></tr><tr><td valign="top">Valid Values</td><td><p>Bit 0:     DKPTM0_2000             Bit 16:    DKPTM10_2010</p><p>Bit 1:     DKPTM1_2001             Bit 17:    DKPTM11_2011</p><p>Bit 2:     DKPTM2_2002             Bit 18:    DKPTM12_2012</p><p>Bit 3:     DKPTM3_2003             Bit 19:    DKPTM13_2013</p><p>Bit 4:     DKPTM4_2004             Bit 20:    DKPTM14_2014</p><p>Bit 5:     DKPTM5_2005             Bit 21:    DKPTM15_2015</p><p>Bit 6:     DKPTM6_2006             Bit 22:    DKPTM16_2016</p><p>Bit 7:     DKPTM7_2007             Bit 23:    DKPTM17_2017</p><p>Bit 8:     DKPTM8_2008             Bit 24:    DKPTM18_2018</p><p>Bit 9:     DKPTM9_2009             Bit 25:    DKPTM19_2019</p><p>Bit 10:  DKPTMA_200A            Bit 26:    DKPTM1A_201A</p><p>Bit 11:  DKPTMB_200B            Bit 27:    DKPTM1B_201B</p><p>Bit 12:  DKPTMC_200C            Bit 28:    DKPTM1C_201C</p><p>Bit 13:  DKPTMD_200D            Bit 29:    DKPTM1D_201D</p><p>Bit 14:  DKPTME_200E             Bit 30:    DKPTM1E_201E</p><p>Bit 15:  DKPTMF_200F             Bit 31:    DKPTM1F_201F</p></td></tr><tr><td valign="top">Default</td><td>None</td></tr></tbody></table>

## Table SSIK-5 - Transaction Key Status - Get Request Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 8104010FD101 841AD101 81072B06010401F609 850102 890AE308E106E104E102C200</td></tr></tbody></table>

## Table SSIK-6 - Transaction Key Status - Get Response Example

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Example (Hex)</td></tr><tr><td valign="top">AA00 8104820FD101 820400000000 8482001ED101 81072B06010401F609 850102 890EE30CE10AE108E106C20400000081</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/configuration/system-status-information-property-group-2.3.1.nnn/system-status-injected-key-information-property-subgroup-2.3.1.1.1.n.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
