> 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/services/qwantifi-tm.md).

# QwantiFi™

QwantiFi is MagTek's MQTT-driven cloud platform for Dyna family hardware, hosted on Magensa to provide complete remote device control across diverse operating systems, browsers, and networks. Once you provision a reader, your point of sale, banking software, access control system, or enterprise backend can dispatch commands and capture responses in real time over the network. This architecture frees your organization from local connectivity barriers, whether you operate an individual terminal or a nationwide fleet. MagTek's Reader Management System handles the heavy lifting by provisioning each unit and automating secure MQTT configuration delivery, as detailed in the architecture and setup sections below.

{% hint style="info" %}
**A Note on "QwantiFi," vs "MQTT":** QwantiFi is built on MQTT, a lightweight, standard messaging protocol for secure device-to-cloud communication. Throughout this documentation we call it "QwantiFi" rather than "MQTT," so you have one consistent name for the service and don't need any prior MQTT knowledge to get started. The underlying protocol is named only where you actually need it, such as in the API reference.
{% endhint %}

### QwantiFi Sections

<table data-header-hidden><thead><tr><th valign="middle"></th><th></th></tr></thead><tbody><tr><td valign="middle"><strong>Reference Section</strong></td><td><strong>Information Available</strong></td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/services/qwantifi/qwantifi-overview"><mark style="color:red;"><strong>QwantiFi Overview</strong></mark></a></td><td>Explains what QwantiFi is and how the device, provisioning, and integrated application pieces fit together, including the supported readers and links to the related guides and API references.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/pos-mqtt-api-reference"><mark style="color:red;"><strong>API Reference</strong></mark></a></td><td>The complete integrated application-facing endpoint surface for QwantiFi on Postman. These endpoints let an integrated application renew its own MQTT credential and look up its devices and topics at runtime. </td></tr></tbody></table>

### Need More Help

{% hint style="info" %}
**Need Help?**

For additional support, please contact MagTek Support:

**Technical Support:**

* 📧 **Email:** [support@magtek.com](mailto:support@magtek.com?subject=Support%20Request)
* 📞 **Phone:** 1-562-546-6800 (US)
* 🕐 **Hours:** Monday-Friday, 5:30 AM - 5:00 PM PST

**Online Resources:**

* 🌐 **Support Portal:** developer.magtek.com

**Documentation Feedback:**

Help us improve this documentation! [feedback@magtek.com](mailto:feedback@magtek.com?subject=Feedback)
{% 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/services/qwantifi-tm.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.