---
title: "Get a list of events"
method: GET
path: "/api/v1/events"
tags: ["Events"]
---

# Get a list of events

`GET /api/v1/events`

The event stream can be queried and filtered by time, priority, sources and tags.

**Notes**:
- If the event you’re querying contains markdown formatting of any kind,
you may see characters such as `%`,`\`,`n` in your output.

- This endpoint returns a maximum of `1000` most recent results. To return additional results,
identify the last timestamp of the last result and set that as the `end` query time to
paginate the results. You can also use the page parameter to specify which set of `1000` results to return.

## Query parameters

- `start` integer, required
- `end` integer, required
- `priority` 'normal' | 'low', nullable — The priority of the event. For example, `normal` or `low`.
- `sources` string
- `tags` string
- `unaggregated` boolean
- `exclude_aggregate` boolean
- `page` integer

## Response `200`

OK

- EventListResponse — An event list response.
  - `events` Event[] — An array of events.
    - `alert_type` 'error' | 'warning' | 'info' | 'success' | 'user_update' | 'recommendation' | 'snapshot' — If an alert event is enabled, set its type. For example, `error`, `warning`, `info`, `success`, `user_update`, `recommendation`, and `snapshot`.
    - `date_happened` integer — POSIX timestamp of the event. Must be sent as an integer (that is no quotes). Limited to events up to 18 hours in the past and two hours in the future.
    - `device_name` string — A device name.
    - `host` string — Host name to associate with the event. Any tags associated with the host are also applied to this event.
    - `id` integer — Integer ID of the event.
    - `id_str` string — Handling IDs as large 64-bit numbers can cause loss of accuracy issues with some programming languages. Instead, use the string representation of the Event ID to avoid losing accuracy.
    - `payload` string — Payload of the event.
    - `priority` 'normal' | 'low', nullable — The priority of the event. For example, `normal` or `low`.
    - `source_type_name` string — The type of event being posted. Option examples include nagios, hudson, jenkins, my_apps, chef, puppet, git, bitbucket, etc. The list of standard source attribute values [available here](https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value).
    - `tags` string[] — A list of tags to apply to the event.
    - `text` string — The body of the event. Limited to 4000 characters. The text supports markdown. To use markdown in the event text, start the text block with `%%% \n` and end the text block with `\n %%%`. Use `msg_text` with the Datadog Ruby library.
    - `title` string — The event title.
    - `url` string — URL of the event.
  - `status` string — A status.

## Other responses

- `400` — Bad Request
- `403` — Authentication Error
- `429` — Too many requests

---

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