BI Tool Integrations

BI Tool Integrations

seeshare's reporting API lets you connect your security data to business intelligence platforms for custom dashboards, trend analysis, and executive reporting. API access requires the Professional tier or higher.

Available Data Endpoints

Three endpoints are available. /api/reporting/scans returns scan summaries with dates, scores, and finding counts in CSV or JSON. /api/reporting/findings returns detailed vulnerability data with CVSS scores, severity, and URLs in CSV or JSON. /api/reporting/trends returns time-series analytics for security score and issue trends in JSON.

Looker Studio

You can connect via a direct PostgreSQL data source (connection details available in Settings) or via the reporting API using a community or custom connector authenticated with your API token. Recommended dashboards include security score trends over time, vulnerability count by severity, domain comparison matrix, and compliance posture overview.

Tableau

You can connect using a Web Data Connector configured to call the seeshare reporting API, or via a direct PostgreSQL connection. Recommended visualizations include a heat map of vulnerabilities by domain and severity, time-series security score trends, a treemap of vulnerability categories, and a scatter plot of CVSS scores versus affected pages.

Power BI

In Power BI Desktop, use Get Data > Web or a Custom Connector and write an M Query to call the reporting API with your Bearer token. Transform the response in Power Query and build your reports from there. Recommended reports include an executive security dashboard, month-over-month compliance trends, a vulnerability aging report, and remediation velocity tracking.

Google Sheets

For a simple setup, use the IMPORTDATA() function with the CSV export URL and your API token directly in a cell. For more advanced use, write a Google Apps Script function that fetches data from the findings endpoint using your API token and writes it to the active sheet. Set up a time-based trigger to run it on a schedule.

Tips

Cache data locally where possible rather than hitting the API on every dashboard refresh. Use query parameters — date range, severity, domain — to filter server-side and reduce data transfer. Consider joining security data with deployment logs, uptime monitoring, or business metrics for deeper insights. Set up BI tool alerts for when security scores drop below defined thresholds.