Flux
Integrations & API

Data API / BI Connectors

Edge

A read-only HTTP feed that pipes your Flux LinkedIn analytics into any tool that can read a URL — Google Sheets, Looker Studio, Power BI, Grafana, or a custom dashboard. Authenticate once with a BI key; get fresh data every time.

How it works

Go to Settings → API to generate a read-only BI key (prefix flux_bi_). From there, a feed picker lets you choose a dataset, granularity, and date range and produces ready-to-paste snippets for Sheets, Power BI, and curl.

Each dataset is a standard HTTP endpoint:

GET https://fluxgraph.app/api/v1/datasets/{dataset}
Authorization: Bearer YOUR_BI_KEY

Because some tools (like Google Sheets' IMPORTDATA) can't set request headers, the key also works as a ?key= query parameter.

Request format=csv for spreadsheet-native output; omit it for JSON. Every endpoint supports a profile_id parameter — pass a comma-separated list to pull data for multiple tracked profiles in one request; each row will include profile_id and profile_name columns.

Available datasets

DatasetGrainDescription
engagement-trendsdaily / weekly / monthlyGap-filled time series — engagement, likes, comments, shares, posts per period
postsone row per postRaw engagement counts, post URL, text, hashtags, format, length, and model-derived adjusted_engagement
overviewone rowScorecard totals for the selected window
breakdownone row per bucketPer-bucket sums by day_of_week, hour, format, or length

Call GET /api/v1/datasets (no dataset name) to get a machine-readable catalog of all available datasets and their accepted parameters.

Connecting to specific tools

Google Sheets — use IMPORTDATA with the CSV URL:

=IMPORTDATA("https://fluxgraph.app/api/v1/datasets/engagement-trends?profile_id=YOUR_PROFILE_ID&granularity=daily&from=-90d&format=csv&key=YOUR_BI_KEY")

The sheet refreshes automatically when you open it. Replace YOUR_PROFILE_ID with the profile ID from your dashboard URL.

Looker Studio — add the CSV endpoint as a URL / Community Connector data source.

Power BI — use Get Data → Web, paste the URL, and set the Authorization header with your BI key.

Key details

  • Auth: BI keys are read-only (flux_bi_ prefix) and separate from MCP keys (flux_ prefix). Generate and revoke both from Settings → API Keys.
  • Rate limit: requests are capped per hour based on your plan's rate_limit_per_hour.
  • Request size: up to 50 profiles per request; trends requests are also capped by a profiles × time-buckets cell limit.
  • Caching: responses include ETag headers — clients that send If-None-Match will receive a 304 Not Modified when data hasn't changed.
  • adjusted_engagement on the posts feed is model-derived (detrended against your posting history) and computed per request — it is not a stored column.

Tips

  • The overview dataset returns one summary row, making it useful as a scorecard widget in Looker Studio or a single-cell KPI in Sheets.
  • If you track multiple profiles, add all their IDs to a single request (profile_id=id1,id2) rather than making separate calls — you stay within rate limits and get a single merged result you can pivot by profile_name.
  • The Settings → API feed picker pre-fills your profile IDs and generates the exact snippet to paste — use it to avoid typos in profile IDs.

Relationship to MCP

The Data API and MCP / API Access use the same Edge-tier gate and the same API key vault, but serve different use cases. MCP is for AI agents (Claude, Cursor) that need to query, search, and score interactively. The Data API is for BI tools and spreadsheets that just need a stable URL returning rows.


Learn more about the Data API →

On this page