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

# get sales velocity event

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

## Request

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

One sales velocity event: its name and description, its window, the adjustment it applies and that adjustment's configuration, the channels it covers, its status and how many items and variants it holds.

`exclude_from_training` says whether the baseline has been told not to learn from this window. A planner sets the mark when the event is created or edited in Tightly, and it is what makes a window already in the past worth recording at all. No operation in this reference sets it. It reads false on an organisation whose events table cannot record the mark, which is the truth there, and on that organisation a save asking for the mark is refused rather than saved without it.

Scope: `sales:read`.

## Path parameters

- `event_id` string, required

## Headers

- `Tightly-Version` string

## Response `200`

The sales velocity event

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

## Other responses

- `400`: Bad Request - Invalid event ID format
- `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 - Database connection or processing errors
- `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)