---
title: "get suggested events"
method: GET
path: "/api/v1/sales/velocity/events/suggested"
tags: ["sales_velocity_events"]
---

# get suggested events

`GET /api/v1/sales/velocity/events/suggested`

## Request

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

The events this organisation's industry is offered for a year, such as Black Friday: each with the real event window, a recommended preparation window (`suggested_start_date` and `suggested_end_date`), the lift range to expect, and whether it has already been dismissed.

`year` picks the year; the set is filtered to the organisation's industry vertical. These are suggestions: nothing here is an event until one is created.

Scope: `sales:read`.

## Query parameters

- `year` integer

## Headers

- `Tightly-Version` string

## Response `200`

List of suggested events for the organization's industry

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

## Other responses

- `400`: Bad Request - Invalid parameters
- `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.
- `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)