From ef4b0fa777266a596fba5b042002fdd0d1b06d71 Mon Sep 17 00:00:00 2001 From: mattwbeard Date: Wed, 28 May 2025 13:20:23 +0100 Subject: [PATCH] Update migrating-to-new-event-types.md --- docs/using-the-api/webhooks/migrating-to-new-event-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using-the-api/webhooks/migrating-to-new-event-types.md b/docs/using-the-api/webhooks/migrating-to-new-event-types.md index 79147050b..b5bdaeff8 100644 --- a/docs/using-the-api/webhooks/migrating-to-new-event-types.md +++ b/docs/using-the-api/webhooks/migrating-to-new-event-types.md @@ -570,7 +570,7 @@ When adopting the new schema, ensure that you handle all elements in the `dataTy Called when initial syncs are complete for all data types queued for a newly connected company, and at least one of those syncs is successful. -The replacement `read.completed.initial` webhook is called the first time the data type is stored in Codat's cache and uses the same payload as the `read.completed` webhook. +The replacement `read.completed.initial` webhook is called the first time a sync is completed after a data connection is linked. Uses the same payload as the `read.completed` webhook. :::tip Adopting the new schema When adopting the new schema, ensure that you handle all elements in the `dataTypes` array to maintain future compatibility.