get sales velocity event
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.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/sales/velocity/events/{event_id}
- Auth: HTTP bearer
Path parameters
Unique identifier of the sales velocity event
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
The sales velocity event
Changes
No recorded changes to this operation across all 1 revision of this API.