---
title: "Interest demand analytics"
description: "Interest demand analytics: available fields, filters, associations, and API operations."
lastModified: "2026-08-21"
---

**Path:** `events/{event_id}/interest-demand-analytics`  
**Methods:** GET collection/record only.

Each record represents a matchmaking interest.

- Fields: `event-id`, `parent-id`, `name`, `metric-version`, `generated-at`, `time-zone`, `joined-registrants-with-selection-count`, `intent-demand`.  
- Filters: `event_id`, `parent_id`, `interest_id`, `intent_id`, `ticket_type_id`, `custom_list_id`.  
- Associations: none.

```
GET .../interest-demand-analytics?parent_id=700&ticket_type_id=301
```

`intent-demand` contains one object per applicable intent:

```json
[
  {
    "intent-id": 801,
    "selection-label": "I can offer",
    "statistics-label": "Supply",
    "paired-intent-id": 802,
    "selected-registrants-count": 42,
    "paired-intent-selected-registrants-count": 57,
    "net-demand": -15
  }
]
```