Skip to main content
GET
/
api
/
analytics
/
workspace
/
timeseries
curl -X GET "https://api.linquid.io/api/analytics/workspace/timeseries?days=30&granularity=day&timezone=America/New_York&currency=USD" \
  -H "Authorization: Bearer <session_or_api_key>" \
  -H "X-Workspace-Id: ws_123"

{
  "success": true,
  "data": {
    "timeseries": [
      {
        "timestamp": "2026-02-20T00:00:00.000",
        "clicks": 182,
        "uniqueVisitors": 149,
        "conversions": 23,
        "revenue": 1164.25
      }
    ],
    "granularity": "day",
    "currency": "USD"
  }
}

​
Time Series Analytics

Use these endpoints to render trend charts with consistent date-range controls.

​
Endpoints

  • GET /api/analytics/workspace/timeseries
  • GET /api/analytics/:linkId/timeseries
  • GET /api/analytics/leads/timeseries
  • GET /api/analytics/sales/timeseries

​
Common query parameters

​
days
number
default:"30"
Rolling lookback window. Server validates and caps range.
​
start
string
Explicit start date/time (overrides inferred start from days when provided with end).
​
end
string
Explicit end date/time.
​
granularity
string
default:"day"
Bucket size for supported endpoints. Accepted values include hour, day, month (invalid values are normalized server-side).
​
timezone
string
default:"workspace timezone or UTC"
IANA timezone used for bucket boundaries.
​
currency
string
Optional display currency for monetary metrics. Unsupported values fall back to workspace/default currency behavior.

​
Request example

curl -X GET "https://api.linquid.io/api/analytics/workspace/timeseries?days=30&granularity=day&timezone=America/New_York&currency=USD" \
  -H "Authorization: Bearer <session_or_api_key>" \
  -H "X-Workspace-Id: ws_123"

​
Response shape

{
  "success": true,
  "data": {
    "timeseries": [
      {
        "timestamp": "2026-02-20T00:00:00.000",
        "clicks": 182,
        "uniqueVisitors": 149,
        "conversions": 23,
        "revenue": 1164.25
      }
    ],
    "granularity": "day",
    "currency": "USD"
  }
}

​
Notes

  • Workspace timeseries combines click and unified conversion streams.
  • Lead and sales timeseries endpoints are conversion-domain specific and should be used for tab-specific analytics views.
  • Cached responses may be briefly stale by design; use refresh/live surfaces for near-real-time monitoring.