---
title: "GET /api/database/views/calendar/{view_id}/"
method: GET
path: "/api/database/views/calendar/{view_id}/"
tags: ["Database table calendar view"]
---

# GET /api/database/views/calendar/{view_id}/

`GET /api/database/views/calendar/{view_id}/`

Responds with serialized rows grouped by date regarding view's date fieldif the user is authenticated and has access to the related workspace.

This is a **premium** feature.

## Path parameters

- `view_id` integer, required

## Query parameters

- `filter__{field}__{filter}` string
- `filter_type` string
- `filters` string
- `from_timestamp` string, date-time, required
- `include` string
- `limit` integer
- `limit_linked_items` integer
- `offset` integer
- `search` string
- `search_mode` string
- `to_timestamp` string, date-time, required
- `user_timezone` string

## Response `200`

- CalendarViewExampleResponse
  - `rows` object, required — Every date bucket (e.g. '2023-01-01') related to the view's date field can have its own entry like this.
  - `field_options` CalendarViewFieldOptions[], required
    - `hidden` boolean — Whether or not the field should be hidden in the card.
    - `order` integer — The order that the field has in the view. Lower value is first.
  - `row_metadata` object — An object keyed by row id with a value being an object containing additional metadata about that row. A row might not have metadata and will not be present as a key if so.

## Other responses

- `400`
- `404`

---

[API](https://skmtc.net/baserow/apis/baserow-api-spec.md) · [All operations](https://skmtc.net/baserow/apis/baserow-api-spec/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/baserow/baserow-api-spec/revisions/ea4a3480f8d3/schema)