Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Connecting to the Security Journey API from Power BI

Explains how to successfully connect Power BI to the Security Journey API by using /svc/public-reporting endpoints to avoid authentication errors caused by HTTP 302 redirects.

Using the Security Journey API with Power BI

When connecting to the Security Journey API from Power BI, you must use specific API endpoints to ensure authentication works correctly.

Why standard API URLs fail

Some Security Journey API endpoints use an HTTP 302 redirect. While most browsers and development tools automatically follow redirects, Power BI’s Web connector does not reliably follow redirects when authentication is required.

As a result, attempts to connect using standard API URLs may fail with an error like:

“We couldn't authenticate with the credentials provided. Please try again.”

This occurs because Power BI tries to authenticate the request before following the redirect, causing the authentication to fail.

How to resolve this

To avoid this issue, use the /svc/public-reporting endpoint instead of the standard /api/v3/public-reporting path.

These endpoints do not rely on redirects and are compatible with Power BI authentication.

Example

Incorrect (redirects and may fail in Power BI): 

https://my.securityjourney.com/api/v3/public-reporting/enrollments
 

Correct (direct endpoint for Power BI): 

https://my.securityjourney.com/svc/public-reporting/enrollments