Skip to main content
MattVF
MattVF
New Member
February 4, 2026
Question

Returning Widget Values from FortiSOAR API call?

  • February 4, 2026
  • 1 reply
  • 99 views

Hi All,

 

I have been trying to get some reporting set up using the FortiSOAR API and have been struggling to find the location of widget data. I can call the dashboards at /api/3/dashboard easily enough but this just returns the wid (I assume this is the UUID for that widget?) and the title with none of the actual values held in the element.

 

When calling the  /api/3/widgets location it just return the widget modules not the actual widgets themselves. This also doesn't seem to  match up the the wid I get from the dashboard either?

 

Does anyone know the location that these wid's are referring to or where dashboard widgets store their data so I can pull it out for our reporting?

 

Currently I am making these calls using the API Endpoints as described here:

https://docs.fortinet.com/document/fortisoar/7.6.5/api-guide/549380/api-endpoints-reference#API_Endpoints_Reference

 

Kind regards,

Matt R

1 reply

enescalban
enescalban
New Member
February 28, 2026

 

Hi Matt,

The dashboard widgets do not expose their rendered values directly via the standard /api/3/widgets or /api/3/dashboard endpoints, as those mainly return definitions, layout metadata, and module information.

However, you can retrieve the actual values by inspecting the network calls the widget makes when it refreshes.

If you:

  1. Open your browser DevTools

  2. Go to the Network tab

  3. Click the widget’s refresh button

  4. Observe the GET request triggered

You will see the exact endpoint the widget calls to fetch its live data.

For example, in the case of the Playbook Execution Monitoring widget, clicking refresh triggers a request like:

 

 
/api/auth/cluster/health?latest=true&section=workflow_vacuum,workflow_mq

Sending a GET request to that endpoint (with proper authentication headers) returns the JSON payload containing the actual values, such as:

 
"workflow_mq": {
...
"total_size": 219
}

That total_size value is what the widget renders (e.g., Queued Workflows = 219).

So instead of using the generic widget endpoints, the recommended approach is:

  • Capture the widget’s backend API call via DevTools

  • Replicate that GET request programmatically

  • Parse the required fields from the JSON response

This allows you to extract the same live data used by the dashboard for reporting purposes.

Hope this helps.

Screenshot_2.pngScreenshot_3.pngScreenshot_4.png

Terms & ConditionsAccessibility statement