---
title: "Get the child events for a given parent event."
method: GET
path: "/_matrix/client/v1/rooms/{roomId}/relations/{eventId}"
tags: ["Event relationships"]
---

# Get the child events for a given parent event.

`GET /_matrix/client/v1/rooms/{roomId}/relations/{eventId}`

## Request

- Base URL: `https://matrix.org`
- URL: `https://matrix.org/_matrix/client/v1/rooms/{roomId}/relations/{eventId}`
- Auth: one of:
  - API key in query parameter `access_token`
  - HTTP bearer
- TypeScript: <https://skmtc.dev/matrix/apis/matrix-client-server-api/docs/_matrix/client/v1/rooms/:roomId/relations/:eventId/get.ts> (a function with typed inputs; its response is checked against the schema)

Retrieve all of the child events for a given parent event.

Note that when paginating the `from` token should be "after" the `to` token in
terms of topological ordering, because it is only possible to paginate "backwards"
through events, starting at `from`.

For example, passing a `from` token from page 2 of the results, and a `to` token
from page 1, would return the empty set. The caller can use a `from` token from
page 1 and a `to` token from page 2 to paginate over the same range, however.

## Path parameters

- `roomId` string, mx-room-id, required
- `eventId` string, mx-event-id, required

## Query parameters

- `from` string
- `to` string
- `limit` integer
- `dir` 'b' | 'f'
- `recurse` boolean

## Response `200`

The paginated child events which point to the parent. If no events are
pointing to the parent or the pagination yields no results, an empty `chunk`
is returned.

- object
  - `next_batch` string: An opaque string representing a pagination token. The absence of this token means there are no more results to fetch and the client should stop paginating.
  - `prev_batch` string: An opaque string representing a pagination token. The absence of this token means this is the start of the result set, i.e. this is the first batch/page.
  - `recursion_depth` integer: If the `recurse` parameter was supplied by the client, this response field is mandatory and gives the actual depth to which the server recursed. If the client did not specify the `recurse` parameter, this field must be absent.
  - `chunk` object[], required: The child events of the requested event, ordered topologically most-recent first.
    - `content` object, required: The body of this event, as created by the client which sent it.
    - `event_id` string, mx-event-id, required: The globally unique identifier for this event.
    - `origin_server_ts` integer, required: Timestamp (in milliseconds since the unix epoch) on originating homeserver when this event was sent.
    - `sender` string, mx-user-id, required: Contains the fully-qualified ID of the user who sent this event.
    - `state_key` string: Present if, and only if, this event is a *state* event. The key making this piece of state unique in the room. Note that it is often an empty string. State keys starting with an `@` are reserved for referencing user IDs, such as room members. With the exception of a few events, state events set with a given user's ID as the state key MUST only be set by that user.
    - `type` string, required: The type of the event.
    - `unsigned` object: Contains optional extra information about the event.
      - `age` integer: The time in milliseconds that has elapsed since the event was sent. This field is generated by the local homeserver, and may be incorrect if the local time on at least one of the two servers is out of sync, which can cause the age to either be negative or greater than it actually is.
      - `membership` string: The room membership of the user making the request, at the time of the event. This property is the value of the `membership` property of the requesting user's [`m.room.member`](https://spec.matrix.org/v1.19/client-server-api#mroommember) state at the point of the event, including any changes caused by the event. If the user had yet to join the room at the time of the event (i.e, they have no `m.room.member` state), this property is set to `leave`. Homeservers SHOULD populate this property wherever practical, but they MAY omit it if necessary (for example, if calculating the value is expensive, servers might choose to only implement it in encrypted rooms). The property is *not* normally populated in events pushed to application services via the application service transaction API (where there is no clear definition of "requesting user").
      - `prev_content` object: The `content` of the previous state event that was replaced by this event. This field is generated by the local homeserver, and is only returned if the event is a state event, and the client has permission to see the previous event.
      - `redacted_because` object: The event that redacted this event, if any.
      - `replaces_state` string, mx-event-id: The event ID of the state event replaced by this event. This field is generated by the local homeserver, and is only returned if the event is a state event. Unlike `prev_content`, this field is included regardless of history visibility.
      - `transaction_id` string: The client-supplied [transaction ID](https://spec.matrix.org/v1.19/client-server-api/#transaction-identifiers), for example, provided via `PUT /_matrix/client/v3/rooms/{roomId}/send/{eventType}/{txnId}`, if the client being given the event is the same one which sent it.
    - `room_id` string, mx-room-id, required: The ID of the room associated with this event.

## Other responses

- `404`: The parent event was not found or the user does not have permission to read this event (it might be contained in history that is not accessible to the user).

---

[API](https://skmtc.dev/matrix/apis/matrix-client-server-api.md) - [All operations](https://skmtc.dev/matrix/apis/matrix-client-server-api/llms.txt) - [OpenAPI document](https://skmtc.dev/matrix/apis/matrix-client-server-api/revisions/c7fe4072c681?raw)