---
title: "Get bigmap key updates"
method: GET
path: "/v1/bigmaps/{id}/keys/{key}/updates"
tags: ["BigMaps"]
---

# Get bigmap key updates

`GET /v1/bigmaps/{id}/keys/{key}/updates`

Returns updates history for the specified bigmap key.

## Path parameters

- `id` integer, required
- `key` string, required

## Query parameters

- `sort` SortParameter
  - `asc` string, nullable — **Ascending** sort mode (optional, i.e. `sort.asc=id` is the same as `sort=id`). \ Specify a field name to sort by. Example: `?sort=balance`.
  - `desc` string, nullable — **Descending** sort mode. \ Specify a field name to sort by descending. Example: `?sort.desc=id`.
- `offset` OffsetParameter
  - `el` integer, nullable — **Elements** offset mode (optional, i.e. `offset.el=123` is the same as `offset=123`). \ Skips specified number of elements. Example: `?offset=100`.
  - `pg` integer, nullable — **Page** offset mode. \ Skips `page * limit` elements. This is a classic pagination. Example: `?offset.pg=1`.
  - `cr` integer, nullable — **Cursor** offset mode. \ Skips all elements with the `cursor` before (including) the specified value. Cursor is a field used for sorting, e.g. `id`. Avoid using this offset mode with non-unique or non-sequential cursors such as `amount`, `balance`, etc. Example: `?offset.cr=45837`.
- `limit` integer
- `micheline` 'Json' | 'JsonString' | 'Raw' | 'RawString'

## Response `200`

- BigMapKeyUpdate[]
  - `id` integer — Internal Id, can be used for pagination
  - `level` integer — Level of the block where the bigmap key was updated
  - `timestamp` string, date-time — Timestamp of the block where the bigmap key was updated
  - `action` string, required — Action with the key (`add_key`, `update_key`, `remove_key`)
  - `value` unknown, required

---

[API](https://skmtc.dev/tzkt/apis/tzkt-api.md) · [All operations](https://skmtc.dev/tzkt/apis/tzkt-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/tzkt/tzkt-api/revisions/a2e2aba5e534/schema)