---
title: "SearchEventTraces searches event trace data by various dimensions."
method: GET
path: "/v1.1/event_traces"
tags: ["ControlService"]
---

# SearchEventTraces searches event trace data by various dimensions.

`GET /v1.1/event_traces`

Please ignore the following lint directives:
 buf:lint:ignore RPC_REQUEST_STANDARD_NAME
 buf:lint:ignore RPC_RESPONSE_STANDARD_NAME

## Query parameters

- `page` integer
- `perPage` integer
- `eventIds` string[], nullable
- `integrationIds` string[], nullable
- `eventNames` string[], nullable
- `statuses` string[], nullable
- `statusReasons` string[], nullable
- `writekeys` string[], nullable
- `integrationNames` string[], nullable
- `omittedFields` string[], nullable

## Response `200`

OK

- ProtobufControlpbV1SearchEventTracesResponse
  - `traces` union[], nullable
    - union
      - object, nullable
      - ProtobufControlpbV1EventTrace
        - `eventId` string
        - `inputEvent` string, byte
        - `integrationId` string
        - `integrationName` string
        - `normalizedEventName` string
        - `outputEvent` string, byte
        - `requestBody` string, byte
        - `requestHeaders` string, byte
        - `response` string, byte
        - `status` 'STATUS_UNSPECIFIED' | 'STATUS_PENDING' | 'STATUS_DELIVERED' | 'STATUS_FILTERED' | 'STATUS_ERROR'
        - `statusReason` string — A short code indicating why an event was given its status. These codes appear in metrics.
        - `timestamp` string, date-time, nullable
        - `writeKey` string

## Other responses

- `4XX` — Something is wrong with your request such as missing or invalid data. Correct your request and try again.
- `5XX` — Internal server error. Try again later or reach out to MetaRouter support.

---

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