---
title: "Update an Event Subscription"
method: PATCH
path: "/v1/event_subscriptions/{id}"
tags: ["Event Subscriptions"]
---

# Update an Event Subscription

`PATCH /v1/event_subscriptions/{id}`

Update an event subscription with the given ID.

## Path parameters

- `id` string, required

## Request body

- object
  - `status` 'active' | 'disabled' | 'deleted' — The status of the event subscription: * active: The event subscription is active and events will be delivered * disabled: The event subscription is temporarily disabled and events will not be delivered * deleted: The event subscription is permanently deleted and events will not be delivered

## Response `200`

Updated

- EventSubscription — Webhooks are event notifications we send to you by HTTPS POST requests. Event Subscriptions are how you configure your application to listen for them.
  - `id` string — The unique identifier for the event subscription
  - `created_at` string, date-time — The date and time the event subscription was created
  - `status` 'active' | 'disabled' | 'deleted' | 'requires_attention' — The status of the event subscription. This indicates if we'll send notifications to this subscription * active: subscription is active and events will be delivered normally * disabled: subscription is temporarily disabled and events will not be delivered * deleted: subscription has been deleted and events will not be delivered * requires_attention: subscription has been disabled due to delivery failures and events will not be delivered
  - `url` string, required — The webhook url where we'll send notifications.
  - `category` 'grant.created' | 'grant.updated' | 'unintegrated_grant.created' | 'unintegrated_grant.updated' | 'disbursement.created' | 'disbursement.updated' | 'inbound_transfer.created' | 'inbound_transfer.updated' | 'donation.created' | 'donation.updated' | 'deposit.created' | 'deposit.updated' | 'verification_request.created' | 'verification_request.updated' — The category of the event. This is useful for filtering events.

## Other responses

- `400` — The request is invalid or contains invalid parameters
- `401` — Unauthorized. The request is missing the security (OAuth2 Bearer token) requirements and the server is unable to verify the identify of the caller.
- `403` — Access denied
- `404` — Resource Not Found
- `500` — Internal Server Error

## Changes

- **2026-06-25** `073f90a1f000` — 15 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 `404` status
  - …11 more
- **2026-06-25** `832437736659` — 15 breaking, 5 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 `404`
  - …16 more
- **2026-03-24** `7d479c5b0de9` — 2 warning
  - added the new `verification_request.created` enum value to the `category` response property for the response status `200`
  - added the new `verification_request.updated` enum value to the `category` response property for the response status `200`

[Change history](https://skmtc.dev/chariot-giving/apis/specs/changes/v1/event_subscriptions/:id/patch.md)

---

[API](https://skmtc.dev/chariot-giving/apis/specs.md) · [All operations](https://skmtc.dev/chariot-giving/apis/specs/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/chariot-giving/specs/revisions/a02db90e18ec/schema)