> For the complete documentation index, see [llms.txt](https://docs.mobiusflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobiusflow.com/help/demos/getting-data-out-from-mobiusflow.md). # Getting Data out from MobiusFlow This section covers different methods on moving your data from MobiusFlow to somewhere else. These methods include via MQTT, via REST and via WebScocket. Pick whichever method best suits your application / integration. ## Engine vs Historian If using REST or WebSockets for data extraction, both Engine and Historian are suitable. Here is a comparison so you know which one to use in any given situation. ### Engine API / Engine WebSocket * Contains telemetry as well as detailed information about MobiusFlow objects relating to MobiusFlow Engine. * Historical data not available, only current data / live updates. * Deeper granular control of which updates to subscribe to when using WebSocket {% hint style="info" %} Note: The Engine API is used for an overall much wider set of applications than just data extraction. It can be used to control everything within the MobiusFlow Engine (backend) including its configuration. See the [main article](/help/mobiusflow-v3/mobiusflow-engine-api-v3.md) on this for a full deep dive on this. {% endhint %} ### Historian API / Historian WebSocket * Data is telemetry / MobiusFlow resource value updates only. No extra engine data. * Full historical data available. * WebSocket allows subscription to all updates only, no granular control --- # 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://docs.mobiusflow.com/help/demos/getting-data-out-from-mobiusflow.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.