---
title: "Changes to List Events"
method: GET
path: "/v1/events"
---

# Changes to List Events

`GET /v1/events`

> Every recorded change to this endpoint, newest first.

## Timeline

Changed in 7 of 41 revisions.

- **2026-06-29** `b87f7738d336` — 8 breaking, 20 info
- **2026-06-29** `c65f43c5ad90` — 4 warning
- **2026-06-25** `f89b4f376e94` — 12 info
- **2026-06-25** `90671617b825` — 12 breaking, 4 info
- **2026-05-18** `4f143792edeb` — 1 breaking, 4 warning, 5 info
- **2026-05-15** `412b6fc0ed4e` — 3 breaking, 3 info
- **2026-05-08** `bdf7c9c5d024` — 6 warning, 6 info

## Changes

- **2026-06-29** `b87f7738d336` — 8 breaking, 20 info
  - removed the required property `code` from the response with the `400` status
  - removed the required property `code` from the response with the `401` status
  - removed the required property `code` from the response with the `403` status
  - removed the required property `code` from the response with the `500` status
  - removed the required property `message` from the response with the `400` status
  - removed the required property `message` from the response with the `401` status
  - removed the required property `message` from the response with the `403` status
  - removed the required property `message` from the response with the `500` status
  - media type `application/json` was changed to a more specific media type `application/problem+json` for the response status `400`
  - media type `application/json` was changed to a more specific media type `application/problem+json` for the response status `401`
  - media type `application/json` was changed to a more specific media type `application/problem+json` for the response status `403`
  - media type `application/json` was changed to a more specific media type `application/problem+json` for the response status `500`
  - added the required property `detail` to the response with the `400` status
  - added the required property `detail` to the response with the `401` status
  - added the required property `detail` to the response with the `403` status
  - added the required property `detail` to the response with the `500` status
  - added the required property `status` to the response with the `400` status
  - added the required property `status` to the response with the `401` status
  - added the required property `status` to the response with the `403` status
  - added the required property `status` to the response with the `500` status
  - added the required property `title` to the response with the `400` status
  - added the required property `title` to the response with the `401` status
  - added the required property `title` to the response with the `403` status
  - added the required property `title` to the response with the `500` status
  - added the required property `type` to the response with the `400` status
  - added the required property `type` to the response with the `401` status
  - added the required property `type` to the response with the `403` status
  - added the required property `type` to the response with the `500` status
- **2026-06-29** `c65f43c5ad90` — 4 warning
  - removed the optional property `details` from the response with the `400` status
  - removed the optional property `details` from the response with the `401` status
  - removed the optional property `details` from the response with the `403` status
  - removed the optional property `details` from the response with the `500` status
- **2026-06-25** `f89b4f376e94` — 12 info
  - added the optional property `details/items/debug` to the response with the `400` status
  - added the optional property `details/items/debug` to the response with the `401` status
  - added the optional property `details/items/debug` to the response with the `403` status
  - added the optional property `details/items/debug` to the response with the `500` status
  - added the optional property `details/items/type` to the response with the `400` status
  - added the optional property `details/items/type` to the response with the `401` status
  - added the optional property `details/items/type` to the response with the `403` status
  - added the optional property `details/items/type` to the response with the `500` status
  - added the optional property `details/items/value` to the response with the `400` status
  - added the optional property `details/items/value` to the response with the `401` status
  - added the optional property `details/items/value` to the response with the `403` status
  - added the optional property `details/items/value` to the response with the `500` status
- **2026-06-25** `90671617b825` — 12 breaking, 4 info
  - the `code` response's property type/format changed from `number`/`` to `string`/`` for status `400`
  - the `code` response's property type/format changed from `number`/`` to `string`/`` for status `401`
  - the `code` response's property type/format changed from `number`/`` to `string`/`` for status `403`
  - the `code` response's property type/format changed from `number`/`` to `string`/`` for status `500`
  - removed the required property `error` from the response with the `400` status
  - removed the required property `error` from the response with the `401` status
  - removed the required property `error` from the response with the `403` status
  - removed the required property `error` from the response with the `500` status
  - removed the required property `timestamp` from the response with the `400` status
  - removed the required property `timestamp` from the response with the `401` status
  - removed the required property `timestamp` from the response with the `403` status
  - removed the required property `timestamp` from the response with the `500` status
  - added the optional property `details` to the response with the `400` status
  - added the optional property `details` to the response with the `401` status
  - added the optional property `details` to the response with the `403` status
  - added the optional property `details` to the response with the `500` status
- **2026-05-18** `4f143792edeb` — 1 breaking, 4 warning, 5 info
  - removed the enum value `donor_account.rejected` from the `query` request parameter `category`
  - added the new `authorization_token.created` enum value to the `results/items/category` response property for the response status `200`
  - added the new `authorization_token.updated` enum value to the `results/items/category` response property for the response status `200`
  - added the new `grant_request.created` enum value to the `results/items/category` response property for the response status `200`
  - added the new `grant_request.updated` enum value to the `results/items/category` response property for the response status `200`
  - added the new enum value `authorization_token.created` to the `query` request parameter `category`
  - added the new enum value `authorization_token.updated` to the `query` request parameter `category`
  - added the new enum value `grant_request.created` to the `query` request parameter `category`
  - added the new enum value `grant_request.updated` to the `query` request parameter `category`
  - removed the `donor_account.rejected` enum value from the `results/items/category` response property for the response status `200`
- **2026-05-15** `412b6fc0ed4e` — 3 breaking, 3 info
  - removed the enum value `donor_account.approved` from the `query` request parameter `category`
  - removed the enum value `grant.approved` from the `query` request parameter `category`
  - removed the enum value `grant.rejected` from the `query` request parameter `category`
  - removed the `donor_account.approved` enum value from the `results/items/category` response property for the response status `200`
  - removed the `grant.approved` enum value from the `results/items/category` response property for the response status `200`
  - removed the `grant.rejected` enum value from the `results/items/category` response property for the response status `200`
- **2026-05-08** `bdf7c9c5d024` — 6 warning, 6 info
  - added the new `donor_account.approved` enum value to the `results/items/category` response property for the response status `200`
  - added the new `donor_account.created` enum value to the `results/items/category` response property for the response status `200`
  - added the new `donor_account.rejected` enum value to the `results/items/category` response property for the response status `200`
  - added the new `donor_account.updated` enum value to the `results/items/category` response property for the response status `200`
  - added the new `grant.approved` enum value to the `results/items/category` response property for the response status `200`
  - added the new `grant.rejected` enum value to the `results/items/category` response property for the response status `200`
  - added the new enum value `donor_account.approved` to the `query` request parameter `category`
  - added the new enum value `donor_account.created` to the `query` request parameter `category`
  - added the new enum value `donor_account.rejected` to the `query` request parameter `category`
  - added the new enum value `donor_account.updated` to the `query` request parameter `category`
  - added the new enum value `grant.approved` to the `query` request parameter `category`
  - added the new enum value `grant.rejected` to the `query` request parameter `category`

---

[Operation](https://skmtc.dev/chariot-giving/apis/specs/docs/v1/events/get.md) · [API](https://skmtc.dev/chariot-giving/apis/specs.md) · [Page](https://skmtc.dev/chariot-giving/apis/specs/changes/v1/events/get)