---
title: "get event analytics"
method: GET
path: "/api/v1/sales/velocity/events/{event_id}/analytics"
tags: ["sales_velocity_events"]
---

# get event analytics

`GET /api/v1/sales/velocity/events/{event_id}/analytics`

## Request

- Base URL: `https://api.app.tightly.io`
- URL: `https://api.app.tightly.io/api/v1/sales/velocity/events/{event_id}/analytics`
- Auth: HTTP bearer

How one sales velocity event performed: baseline (the forecast without it), target (the forecast adjusted for it) and actual units, revenue, profit and return on investment, with an accuracy figure.

`event_id` is the event. Omit `group_by` for one aggregate row over the event period, or send `group_by=date` for one row per calendar day.

Scope: `sales:read`.

## Path parameters

- `event_id` string, required

## Query parameters

- `group_by` 'date'

## Headers

- `Tightly-Version` string

## Response `200`

The event's analytics

- SalesVelocityEventsApiResponse
  - `data` unknown
  - `message` SalesVelocityEventsApiMessage
    - `desc` string
    - `service` string
    - `severity` 'SUCCESS' | 'INFO' | 'ERROR' | 'WARNING'

## Other responses

- `400`: Bad Request - Invalid group_by value
- `401`: No usable key: malformed, unknown, revoked, expired or stopped. One refusal covers all five, telling a caller which is which maps the surface for them. A request with no Authorization header at all is refused 400 before any key is looked for.
- `403`: The key may not reach this operation. `scope_missing` when the key does not hold Sales; `organization_mismatch` when the path names an organisation that is not the key's; `ip_not_allowed` when the caller's address is outside the key's allowlist.
- `404`: Not Found - Sales velocity event with specified ID does not exist
- `429`: The key has spent its allowance for this minute. 600 reads and 120 writes a minute, counted per key, refused calls included. `Retry-After` says how long to wait.
- `500`: Internal Server Error
- `503`: The database is briefly out of reach, which is what a failover or a full connection pool looks like from outside. Wait the seconds `Retry-After` names and send the request again. A read is safe to repeat. A write is not, because the connection was lost in the middle of it, so read the object back before sending it a second time. Branch on the status rather than on `code`, which is `POSTGRES_UNAVAILABLE` from one of the two seams that raise this and `SERVICE_UNAVAILABLE` from the other.

---

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