How to Link Power BI with vNode Using API Queries

Created by Jose Fabian Solano, Modified on Tue, 22 Jul at 9:31 PM by Jose Fabian Solano

 Connecting Power BI Desktop to vNode via REST API


✅ Prerequisites

Before starting, ensure the following:

  • vNode is installed and running

  • The REST API Server module is properly configured and active

  • Simulated or real data is being published by vNode

? You can follow this official guide to configure the REST API module in vNode:
? https://vesterbusiness.freshdesk.com/a/solutions/articles/44002581366


? Step 1: Determine Your vNode REST Endpoint URL

If you're using the default configuration, vNode serves its REST API on port 3003. Your base URL will look like:

cpp
CopyEdit
http://<VNODE_IP>:3003

Local example:

cpp
CopyEdit
http://127.0.0.1:3003

? Step 2: Create a Web Query in Power BI Desktop

  1. Open Power BI Desktop.

  2. Click Get Data from the toolbar.

  3. Choose Web as the data source.



  4. In the input field, enter the full REST API URL for the vNode tag or group of tags you want to read.


? Example: Real-Time Tag Query

To retrieve the real-time value of a tag from vNode, you can use the following format:

bash
CopyEdit
http://127.0.0.1:3003/tags?cmd=read&path="Your/Tag/Path"

This returns a JSON object containing the tag’s value, quality, and timestamp.

? You can also request multiple tags by using a group path.
Refer to the REST API Server documentation in vNode to explore all available endpoints and methods.



?️ Recommendations

  • Ensure your firewall allows communication through port 3003.

  • If Power BI prompts for authentication, select Anonymous (unless you’ve enabled credentials in vNode).

  • Use the Power BI Query Editor to shape and transform the JSON response into structured tables.




Created By JF


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article