> 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/technical-docs/mobiusflow-services/juniper-mist.md).

# Juniper Mist

Explaining how to use MobiusFlow Juniper Mist service to pull BLE data from the Mist network into MobiusFlow

The MobiusFlow Juniper Mist service works by interfacing with a given site on the Juniper Mist cloud. It is currently not possible to connect directly to a Mist AP due to limitations of the Mist network itself.

The service is used to subscribe to BLE data updates within the Mist cloud.

{% hint style="info" %}
Note: For full data decryption, this service is designed to be used in conjunction with a BLE devices service. See [section explaining this](#use-with-ble-devices-service).
{% endhint %}

## Requirements from Mist Cloud

Find the following in Mist Cloud:

* **Site ID**: Most easily found by looking in the URL when browsed to the site on the Mist portal. The URL's take the form of https\://**\<HOSTNAME>**/admin/?org\_id=\<ORG\_ID>#!psk/**\<SITE\_ID>**.
* **Region**: Use the **HOSTNAME** in the URL and the following table to find the region.

<table data-search="false"><thead><tr><th>HOSTNAME</th><th>Region</th></tr></thead><tbody><tr><td>manage.mist.com</td><td>Global 01</td></tr><tr><td>manage.gc1.mist.com</td><td>Global 02</td></tr><tr><td>manage.ac2.mist.com</td><td>Global 03</td></tr><tr><td>manage.gc2.mist.com</td><td>Global 04</td></tr><tr><td>manage.gc4.mist.com</td><td>Global 05</td></tr><tr><td>manage.eu.mist.com</td><td>EMEA 01</td></tr><tr><td>manage.gc3.mist.com</td><td>EMEA 02</td></tr><tr><td>manage.ac6.mist.com</td><td>EMEA 03</td></tr><tr><td>manage.gc6.mist.com</td><td>EMEA 04</td></tr><tr><td>manage.ac5.mist.com</td><td>APAC 01</td></tr><tr><td>manage.gc5.mist.com</td><td>APAC 02</td></tr><tr><td>manage.gc7.mist.com</td><td>APAC 03</td></tr></tbody></table>

* **Mist Authentication Key**: This can be created on the Mist portal in **Organization > Settings > API Token > Create Token**.

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FFOA26ziQruEwVFr0qZ6G%2Fimage.png?alt=media&amp;token=1ac05f81-5a19-42f5-8703-5c0041aad889" alt=""><figcaption></figcaption></figure>

For most secure setup we recommend scoping the new API key as **Observer** of a **Specific Site** (the Site you're connecting to here).

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FLa67eU0u2ft6SUZ9Mlfi%2Fimage.png?alt=media&amp;token=66f11b83-0c1c-416d-ac12-b96be430b2ca" alt=""><figcaption></figcaption></figure>

## Configuration the Service

Add a Juniper Mist service to your MobiusFlow configuration:

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FeLaSqrOIaYROJJ27R2IM%2FScreenshot%202026-09-23%20at%2016.47.28.png?alt=media&amp;token=76291d15-9264-49da-ace8-18b74c26746a" alt=""><figcaption></figcaption></figure>

Open the service settings of the new service:

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2F8uK0X8MTfuYz55yxPmIV%2FScreenshot%202026-09-23%20at%2016.48.01.png?alt=media&amp;token=ef27f4fb-c7ad-4393-96bb-5c9da76344d8" alt=""><figcaption></figcaption></figure>

Populate the settings you acquired from the Mist portal + Save:

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FSUzZKc8bEPrK8QP8sqB6%2FScreenshot%202026-09-23%20at%2016.49.05.png?alt=media&amp;token=aefdc153-6adb-402c-b442-b26e5d6759cb" alt=""><figcaption></figcaption></figure>

Start the now configure service:

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FQVFCVbBkxfHnOpxMCprB%2FScreenshot%202026-09-23%20at%2016.49.57.png?alt=media&amp;token=0a41c73b-7d84-4413-a1c8-48f66931d852" alt=""><figcaption></figcaption></figure>

If the service connects and is operating correctly it will show:

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FiAreJvpdol4uWjVHBcZT%2FScreenshot%202026-09-23%20at%2016.50.56.png?alt=media&amp;token=1e7d45c7-4a68-4f1c-bc1a-7bd731361223" alt=""><figcaption></figcaption></figure>

## Use with BLE Devices service

The Juniper Mist service simply forwards raw BLE data. It does not perform any decoding. As such, once the service has received the data, it is forwarded to the MobiusFlow hub (via a BCMD BLE\_RX command). The hub will forward the data to any listening BLE devices services. The BLE devices service is where the raw BLE data is decoded and MobiusFlow objects are populated. [See full article on the BLE devices service here](/help/technical-docs/mobiusflow-services/ble-devices.md).

This means, to implement full end-to-end data transfer and decoding, this service is designed to be used in conjunction with the BLE Devices service.


---

# 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/technical-docs/mobiusflow-services/juniper-mist.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.