---
title: "List calendar events"
method: GET
path: "/events"
tags: ["Events"]
---

# List calendar events

`GET /events`

## Request

- Base URL: `https://app.fareeqy.com/api/v1`
- URL: `https://app.fareeqy.com/api/v1/events`
- Auth: HTTP bearer

Every event on the key's company calendar, whoever organized it. Defaults
to upcoming only; an explicit `from`/`to` window wins over `include_past`. Bounds and the
"upcoming" cutoff resolve in the company time zone. Requires operation
`events:read`.

## Query parameters

- `from` string
- `to` string
- `include_past` boolean
- `limit` integer
- `offset` integer

## Response `200`

A page of events.

- object
  - `meta` object
    - `total` integer: The full unfiltered count.
    - `limit` integer
    - `offset` integer
    - `count` integer: Records in the returned page.
  - `data` Event[]
    - `id` integer: Numeric id (events have no slug).
    - `url` string, nullable: Absolute address of the page a person opens in فريقي.
    - `name` string
    - `description` string, nullable
    - `starts_at` string, date-time
    - `ends_at` string, date-time
    - `all_day` boolean
    - `meeting_url` string, nullable
    - `organizer` string, nullable: The person who organized the event. A key can edit or delete any event in its company, whoever organized it.
    - `organizer_email` string, nullable
    - `attendees` UserRef[]
      - `name` string
      - `email` string, email

## Other responses

- `401`: Missing or invalid API key.
- `403`: Two different refusals share this status, and a client must tell them apart by `error.code`. `forbidden` means the key's scope or allowlist does not permit this operation, or Pundit denied the action. `plan_upgrade_required` means the company's plan carries no API access at all, so no key on it can ever succeed and there is nothing to retry.
- `404`: Resource not found or not accessible — also returned for EVERY endpoint when the company's `rest_api` feature flag is disabled (the surface is hidden). Lookups drill through the URL hierarchy, so another company's record is a 404 and never a leak. A path that matches no route at all answers 404 with the distinct code `unknown_endpoint` and echoes the path back, so a mistyped or half-built URL is told apart from a record that is missing or out of reach.
- `422`: A caller-fixable bad request (validation error, bad date, bad enum).
- `429`: Either the company's daily API allowance is spent (`rate_limit_exceeded`), or the per-key / per-IP burst throttle of 300 requests per minute fired. Both come back after a wait, so `Retry-After` is honest here. **The two bodies are not the same shape.** The daily-quota refusal uses the standard error envelope. The burst throttle is served by Rack::Attack ahead of the application, so its body is a flat `{"error": "<string>"}` with no `code`. A client that reads `error.code` has to tolerate `error` being a plain string.

---

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