---
title: "Search RUM events"
method: POST
path: "/api/v2/rum/events/search"
tags: ["RUM"]
---

# Search RUM events

`POST /api/v2/rum/events/search`

List endpoint returns RUM events that match a RUM search query.
[Results are paginated][1].

Use this endpoint to build complex RUM events filtering and search.

[1]: https://docs.datadoghq.com/logs/guide/collect-multiple-logs-with-pagination

## Request body

- RUMSearchEventsRequest — The request for a RUM events list.
  - `filter` RUMQueryFilter — The search and filter query settings.
    - `from` string — The minimum time for the requested events; supports date (in [ISO 8601](https://www.w3.org/TR/NOTE-datetime) format with full date, hours, minutes, and the `Z` UTC indicator - seconds and fractional seconds are optional), math, and regular timestamps (in milliseconds).
    - `query` string — The search query following the RUM search syntax.
    - `to` string — The maximum time for the requested events; supports date (in [ISO 8601](https://www.w3.org/TR/NOTE-datetime) format with full date, hours, minutes, and the `Z` UTC indicator - seconds and fractional seconds are optional), math, and regular timestamps (in milliseconds).
  - `options` RUMQueryOptions — Global query options that are used during the query. Note: Only supply timezone or time offset, not both. Otherwise, the query fails.
    - `time_offset` integer — The time offset (in seconds) to apply to the query.
    - `timezone` string — The timezone can be specified as GMT, UTC, an offset from UTC (like UTC+1), or as a Timezone Database identifier (like America/New_York).
  - `page` RUMQueryPageOptions — Paging attributes for listing events.
    - `cursor` string — List following results with a cursor provided in the previous query.
    - `limit` integer — Maximum number of events in the response.
  - `sort` 'timestamp' | '-timestamp' — Sort parameters when querying events.

## Response `200`

OK

- RUMEventsResponse — Response object with all events matching the request and pagination information.
  - `data` RUMEvent[] — Array of events matching the request.
    - `attributes` RUMEventAttributes — JSON object containing all event attributes and their associated values.
      - `attributes` object — JSON object of attributes from RUM events.
      - `service` string — The name of the application or service generating RUM events. It is used to switch from RUM to APM, so make sure you define the same value when you use both products.
      - `tags` string[] — Array of tags associated with your event.
      - `timestamp` string, date-time — Timestamp of your event.
    - `id` string — Unique ID of the event.
    - `type` 'rum' — Type of the event.
  - `links` RUMResponseLinks — Links attributes.
    - `next` string — Link for the next set of results. Note that the request can also be made using the POST endpoint.
  - `meta` RUMResponseMetadata — The metadata associated with a request.
    - `elapsed` integer — The time elapsed in milliseconds.
    - `page` RUMResponsePage — Paging attributes.
      - `after` string — The cursor to use to get the next results, if any. To make the next request, use the same parameters with the addition of `page[cursor]`.
    - `request_id` string — The identifier of the request.
    - `status` 'done' | 'timeout' — The status of the response.
    - `warnings` RUMWarning[] — A list of warnings (non-fatal errors) encountered. Partial results may return if warnings are present in the response.
      - `code` string — A unique code for this type of warning.
      - `detail` string — A detailed explanation of this specific warning.
      - `title` string — A short human-readable summary of the warning.

## Other responses

- `400` — Bad Request
- `403` — Not Authorized
- `429` — Too many requests

---

[API](https://skmtc.net/datadog/apis/api-v2.md) · [All operations](https://skmtc.net/datadog/apis/api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/datadog/api-v2/versions/da68bf029e4c/schema)