---
title: "Usage detail for one event name"
method: GET
path: "/v1/events/{name}/usage"
tags: ["Events"]
---

# Usage detail for one event name

`GET /v1/events/{name}/usage`

## Request

- Base URL: `https://api.volanea.com`
- URL: `https://api.volanea.com/v1/events/{name}/usage`
- Auth: HTTP bearer

One event name's totals: how many times it fired, how many distinct contacts triggered it, and when it was first and last seen.

`contactCount` counts only events that were attributed to a contact — events tracked without a resolvable address raise `count` without raising it, so the two legitimately disagree.

An unknown name answers 200 with zeros rather than 404, so this endpoint cannot tell you "never fired" from "you misspelled it". When a trigger looks dead, check `GET /v1/events/names` for what you are actually sending.

Takes the same optional window as `GET /v1/events/stats`, so drilling from a ranged list into one name keeps the range and the two agree. With no range this covers all time, as it always has.

## Path parameters

- `name` string, required

## Query parameters

- `days` integer
- `from` string, date-time
- `to` string, date-time

## Response `200`

Usage detail.

- object
  - `name` string
  - `count` integer
  - `contactCount` integer: Distinct contacts that triggered this event.
  - `firstSeen` integer, nullable
  - `lastSeen` integer, nullable

## Other responses

- `401`: Missing or invalid API key.
- `422`: Request validation failed (code `validation_error`, 422).

---

[API](https://skmtc.dev/volanea/apis/volanea-api.md) · [All operations](https://skmtc.dev/volanea/apis/volanea-api/llms.txt) · [OpenAPI document](https://skmtc.dev/volanea/apis/volanea-api/revisions/9e187ae84fda?raw)