# Removal of Deprecated Case Events

## Summary

Peach is removing two deprecated webhook events—`case.created` and `case.updated`—from active event firing. A similar event, `case.deleted` was in the documentation but had never been fired.These events were deprecated in favor of the unified `case.changed` event, which has been available since January 2024. After the removal date, these deprecated events will no longer be fired for new activity. Historical event data will remain available for querying.

## Timeline

- **Replacement Event Available:** January 2024 (`case.changed` has been active since this date)
- **Deprecated Events Removed:** March 20, 2026
- **Historical Data:** Deprecated events that were previously recorded will remain queryable after the removal date. Only new event firing will stop.


## What Is Changing

Peach will stop firing the following deprecated case-related events:

| Deprecated Event | Status | Replacement |
|  --- | --- | --- |
| `case.created` | Will no longer be fired | `case.changed` with `changeType: "create"` |
| `case.deleted` | Was never fired | `case.changed` with `changeType: "delete"` |
| `case.updated` | Will no longer be fired | `case.changed` with `changeType: "update"` |


The `case.changed` event consolidates all case lifecycle activity into a single event type. It includes a `changeType` field (indicating whether the case was created, updated, or deleted) and a `jsonPatch` field containing the specific details of what changed on the case.

## Why We Are Making This Change

- **Consolidation:** The `case.changed` event replaces three separate events with a single, unified event that provides richer detail about what changed and why.
- **Improved Data:** The deprecated events returned empty content payloads (`{"content":{}}`). The replacement event includes structured change data via the `jsonPatch` field, giving you visibility into exactly what was modified.
- **Cleanup:** These events have been identified as deprecated in the API documentation. Removing them reduces noise in event logs and aligns system behavior with the documented API.


## What You Need To Do

If your integration consumes case events via webhooks or event queries, review your implementation for references to the deprecated event types and update them to use `case.changed` instead.

1. **Audit your integration code** for any references to `case.created`, `case.deleted`, or `case.updated`.
2. **Update event handlers** to listen for `case.changed` and use the `changeType` field to distinguish between created, updated, and deleted cases.
3. **Update any event queries** that filter by the deprecated event types to filter by `case.changed` instead. **Note:** For cases associated with loans that predate January 2024, historical activity may only be recorded under the deprecated event types. You may still need to reference these older events when querying historical data from that period.
4. **Test your updated integration** to confirm your workflows respond correctly to the `case.changed` event structure before the removal date.


If you are not currently using webhooks or querying for these specific event types, no action is required on your part.

## Frequently Asked Questions

**Will there be any downtime or service interruption?**

No. This change only affects event firing. All case management functionality—creating, updating, and deleting cases—continues to work exactly as it does today. Only the event types generated by these actions are changing.

**What happens to historical events that were already recorded?**

Historical event records for `case.created`, `case.deleted`, and `case.updated` will remain in the events table and can still be queried. Only new event firing will stop after the removal date.

**How do I know if my integration is affected?**

Check whether your webhook configurations or event query logic references `case.created`, `case.deleted`, or `case.updated`. If you have registered webhooks for these event types or filter events by these types in API calls, you will need to update your integration. If you are unsure, contact Peach support for assistance.

**What does the case.changed event payload look like?**

The `case.changed` event includes:

- A `changeType` field indicating the action: `"create"`, `"update"`, or `"delete"`
- A `jsonPatch` field containing the specific changes made to the case (for updates)


Refer to the [Events API documentation](https://docs.peachfinance.com/api-docs/api-public/events) for more information.

**Will case.changed still fire with empty diffs?**

No. As part of this update, `case.changed` will no longer fire when no actual changes are made to a case. Previously, certain no-op API calls could generate events with empty `jsonPatch` payloads. This has been resolved.

**Has case.changed been available this entire time?**

Yes. The `case.changed` event has been active since January 2024. It has been running in parallel with the deprecated events during this transition period.

## Next Steps

Customer Success will be available to:

1. Answer questions about the change and help assess whether your integration is affected
2. Assist with identifying references to deprecated events in your webhook configurations
3. Coordinate testing and validation of your updated integration before the removal date


## Questions

Contact [support@peachfinance.com](mailto:support@peachfinance.com)