---
title: "Get events by event handle"
method: GET
path: "/accounts/{address}/events/{event_handle}/{field_name}"
tags: ["Events"]
---

# Get events by event handle

`GET /accounts/{address}/events/{event_handle}/{field_name}`

This API extracts event key from the account resource identified
by the `event_handle_struct` and `field_name`, then returns
events identified by the event key.

## Path parameters

- `address` string, hex, required — Hex encoded 32 byte Aptos account address
- `event_handle` string, required — String representation of a MoveStructTag (on-chain Move struct type). This exists so you can specify MoveStructTags as path / query parameters, e.g. for get_events_by_event_handle. It is a combination of: 1. `move_module_address`, `module_name` and `struct_name`, all joined by `::` 2. `struct generic type parameters` joined by `, ` Examples: * `0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>` * `0x1::account::Account` Note: 1. Empty chars should be ignored when comparing 2 struct tag ids. 2. When used in an URL path, should be encoded by url-encoding (AKA percent-encoding). See [doc](https://aptos.dev/concepts/basics-accounts) for more details.
- `field_name` string, required

## Query parameters

- `start` string, uint64 — A string containing a 64-bit unsigned integer. We represent u64 values as a string to ensure compatability with languages such as JavaScript that do not parse u64s in JSON natively.
- `limit` integer

## Response `200`

- VersionedEvent[]
  - `version` string, uint64, required — A string containing a 64-bit unsigned integer. We represent u64 values as a string to ensure compatability with languages such as JavaScript that do not parse u64s in JSON natively.
  - `key` string, hex, required — Event key is a global index for an event stream. It is hex-encoded BCS bytes of `EventHandle` `guid` field value, which is a combination of a `uint64` creation number and account address (without trimming leading zeros). For example, event key `0x000000000000000088fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1` is combined by the following 2 parts: 1. `0000000000000000`: `uint64` representation of `0`. 2. `88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1`: 32 bytes of account address.
  - `sequence_number` string, uint64, required — A string containing a 64-bit unsigned integer. We represent u64 values as a string to ensure compatability with languages such as JavaScript that do not parse u64s in JSON natively.
  - `type` string, required — String representation of an on-chain Move type tag that is exposed in transaction payload. Values: - bool - u8 - u64 - u128 - address - signer - vector: `vector<{non-reference MoveTypeId}>` - struct: `{address}::{module_name}::{struct_name}::<{generic types}>` Vector type value examples: - `vector<u8>` - `vector<vector<u64>>` - `vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>` Struct type value examples: - `0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin> - `0x1::account::Account` Note: 1. Empty chars should be ignored when comparing 2 struct tag ids. 2. When used in an URL path, should be encoded by url-encoding (AKA percent-encoding).
  - `data` unknown, required

## Other responses

- `400`
- `404`
- `500`

## Changes

- **2022-08-07** (v1) `2953a57ebb77` — 1 info
  - added the required property `items/version` to the response with the `200` status
- **2022-08-01** (v1) `ad82919b4797` — 15 warning, 18 info
  - added the new `bcs_serialization_error` enum value to the `error_code` response property for the response status `400`
  - added the new `bcs_serialization_error` enum value to the `error_code` response property for the response status `404`
  - added the new `bcs_serialization_error` enum value to the `error_code` response property for the response status `500`
  - added the new `invalid_bcs_in_storage_error` enum value to the `error_code` response property for the response status `400`
  - …29 more
- **2022-08-01** (v1) `5db9ba580d74` — 4 breaking, 3 info
  - added the pattern `^0x[0-9a-zA-Z:_<>]+$` to the `path` request parameter `event_handle`
  - for the `path` request parameter `address`, the type/format was changed from `string`/`` to `string`/`hex`
  - for the `query` request parameter `start`, the type/format was changed from `string`/`` to `string`/`uint64`
  - the `items/type` response's property type/format changed from `object`/`` to `string`/`` for status `200`
  - …3 more

[Change history](https://skmtc.dev/apscan/apis/aptos-node-api/changes/accounts/:address/events/:event_handle/:field_name/get.md)

---

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