> 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/~/revisions/AxjZXnxcrmQygHeCLIf3/dynafamily-programmers-manual/about-the-dynafamily-programmers-manual.md).
# About The DynaFamily Programmer's Manual
These pages detail how to communicate with Secure Card Reader Authenticator devices which implement MagTek Messaging Schema (MMS) and the DynaFlex family, DynaFlex II Go and DynaProx system architecture.
These pages also describe how to communicate with PIN Entry Devices (PED) which implement MagTek Messaging Schema (MMS) and the DynaFlex/DynaProx family system architecture. (PED ONLY)
These pages use **bold face** to:
* Highlight terms / concepts being formally defined in the current sentence / paragraph
* Highlight important distinguishing keywords in sentences
* Indicate hyperlinks to other sections / tables
These pages use a small number of annotation standards that are important to understand:
* Hexadecimal values are prefixed with **0x** unless the context clearly indicates an un-prefixed number is hexadecimal (for example, TLV tags, lengths, and values are always assumed to be hex).
* Binary values are prefixed with **0b** unless the context clearly indicates the value is binary.
* Decimal values are not prefixed unless required for clarity, in which case the prefix is **0d**.
The standard documented by these pages makes extensive use of Tag-Length-Value encoding. [**Tag-Length-Value (TLV) Encoding** ](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects)describes how to encode and decode TLV, and how to read the tables in this document that describe TLV data objects.
## See Also
* [**Tag-Length-Value (TLV) Encoding** ](/api-and-command-reference/~/revisions/AxjZXnxcrmQygHeCLIf3/dynafamily-programmers-manual/data-types-and-shared-tlv-data-objects.md)
{% hint style="info" %}
**Need Help?**
For additional support, please contact MagTek Support:
**Technical Support:**
* 📧 **Email:**
* 📞 **Phone:** 1-800-788-6835 (US) | +1-562-546-6616 (International)
* 🕐 **Hours:** Monday-Friday, 6:00 AM - 5:00 PM PST
**Online Resources:**
* 🌐 **Official Site:** [https://www.magtek.com](https://www.magtek.com/)
* 💬 **Developer Forum:** [https://forum.magtek.com](https://forum.magtek.com/)
**Documentation Feedback:**
Help us improve this documentation! [Submit feedback](broken://spaces/1lWLescKFIPsMeIJI6Cd/pages/5314c528980689961380bea0044c1256aaeb39bc)
{% endhint %}
---
# 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://developer.magtek.com/api-and-command-reference/~/revisions/AxjZXnxcrmQygHeCLIf3/dynafamily-programmers-manual/about-the-dynafamily-programmers-manual.md?ask=&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.