> 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/qwantifi-api-and-command-reference.md).

# QwantiFi API & Command Reference

This reference documents the QwantiFi APIs — the endpoints, request and response shapes, and status codes for both sides of the QwantiFi flow. Use the API Reference for the endpoints a point-of-sale application calls at runtime, and the RMS MQTT Configuration API Reference for the server-side provisioning endpoints that configure a device and place it on the broker. 

For the concepts behind these calls, see the [<mark style="color:red;">**QwantiFi guides**</mark>](https://developer.magtek.com/guides/guides/qwantifi).

### In This Section

| **Section**                                                                                                                                                                                                                                    | **Information**                                                                                                                                                                             |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [<mark style="color:red;">**POS MQTT API Reference**</mark>](https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/pos-mqtt-api-reference)[ ](/api-and-command-reference/dynafamily-programmers-manual.md) | Documents the four endpoints an integrated application uses to refresh its MQTT credential and look up its devices, topics, and device status, including request shapes and response codes. |
| [<mark style="color:red;">**RMS MQTT Configuration API Reference**</mark>](https://developer.magtek.com/api-and-command-reference/qwantifi-api-and-command-reference/rms-mqtt-configuration-api-reference)                                     | Documents the provisioning endpoints that retrieve a device's MQTT configuration and credentials, return the commands that update the reader, and record the result.                        |

### Need More Help

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

For additional support, please contact MagTek Support:

**Technical Support:**

* 📧 **Email:** <support@magtek.com>
* 📞 **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/qwantifi-api-and-command-reference.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.