Get one deal's analytics overview

GET/analytics/deals/{deal_id}/overview

analytics:read get_deal_analytics_overviewRead-only

Returns one deal's details with its engagement events: the total, distinct people, and per category.

Use GET /analytics/deals/{id} across many deals. The deal must be one GET /deals lists for you, else 404. Deal fields come from the deal; funding_sought and the counts come from the analytics store, which trails live data, so an unsynced deal has a null funding_sought and zero events. Query parameters are ignored. It only reads.

Path parameters

deal_idstring (uuid)Required#
The deal's id, as GET /deals returns it.

Responses

200

The overview.

AnalyticsOverview

{
  "data": {
    "deal_guid": "9f3b6e2a-4c7d-4a1e-9b2f-8d0c1a3e5f70",
    "name": "Series B - Meridian Renewables",
    "status": "published",
    "asset_class": "private_equity",
    "structure": "equity",
    "funding_sought": 5000000,
    "currency": "GBP",
    "published_on": "2026-02-14T09:30:00Z",
    "engagement": {
      "event_count": 1842,
      "viewer_count": 137,
      "by_category": [
        {
          "key": "deal",
          "value": 1650
        },
        {
          "key": "transaction",
          "value": 192
        }
      ]
    }
  }
}

401

Authentication failed. error.code is one of invalid_token, expired, revoked.

Error

403

Authorization failed. error.code is one of org_disabled, ip_blocked, missing_scope, scope_disabled, user_disabled.

Error

404

Resource not found (error.code = not_found).

Error

429

Rate limit exceeded (error.code = rate_limited).

Error

Examples

curl https://your-org-domain/kong/core/api/v2/analytics/deals/{deal_id}/overview\
  -H "Authorization: Bearer $HELM_API_KEY"\
  -H "Content-Type: application/json"