From 7b5015a599b3a9252d3982b65294c2465ceb085a Mon Sep 17 00:00:00 2001 From: Polina <112084241+pzaichkina@users.noreply.github.com> Date: Thu, 7 Mar 2024 10:59:44 +0000 Subject: [PATCH] Update migration-guide-advanced.md --- .../webhooks/migration-guide-advanced.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/using-the-api/webhooks/migration-guide-advanced.md b/docs/using-the-api/webhooks/migration-guide-advanced.md index 46001159b..5bb9c3897 100644 --- a/docs/using-the-api/webhooks/migration-guide-advanced.md +++ b/docs/using-the-api/webhooks/migration-guide-advanced.md @@ -10,15 +10,15 @@ If you are considering using Codat's new webhook management endpoints, check tha | I am using... | Action and impact | |----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ...email notification functionality | * Do not migrate to the new webhook service
* Review the [critical considerations](/using-the-api/webhooks/migration-guide-advanced#email-notification-functionality) | -| ...event log endpoints (e.g. `/rules/alerts`) | * Do not migrate until you have removed all calls to logs endpoints from your application logic
* Review the [critical considerations](/using-the-api/webhooks/migration-guide-advanced#event-log-endpoints) | -| ...`RuleId` in my application's existing logic | * Do not migrate until you have removed all application logic using the `RuleId` property
* Review the [critical considerations](/using-the-api/webhooks/migration-guide-advanced#ruleid-in-existing-logic) | -| ...only company-agnostic webhook functionality | * Request to migrate to the new webhook service
| -| ...company-specific webhook functionality | * Request to migrate to the new webhook service
* Review the [additional considerations](/using-the-api/webhooks/migration-guide-advanced#company-specific-webhooks) | -| ...`X-Codat-ClientId` header to determine the source Codat instance of the event | * Request to migrate to the new webhook service
* Configure a custom header, as described in [additional considerations](/using-the-api/webhooks/migration-guide-advanced#source-client-header) | -| ...webhook auth header via the `/profile` endpoint | * Request to migrate to the new webhook service
* Configure a custom header using the Portal, as described in [additional considerations](/using-the-api/webhooks/migration-guide-advanced#webhook-auth-header) | -| ...webhook auth header via the Portal | * Request to migrate to the new webhook service
* Configure a custom header using the Portal, as described in [additional considerations](/using-the-api/webhooks/migration-guide-advanced#webhook-auth-header) | -| ...`Retry-After` header to control the time between retries | * Request to migrate to the new webhook service
* Review the [additional considerations](/using-the-api/webhooks/migration-guide-advanced#retry-after-header) | +| ...email notification functionality | - Do not migrate to the new webhook service
- Review the [critical considerations](/using-the-api/webhooks/migration-guide-advanced#email-notification-functionality) | +| ...event log endpoints (e.g. `/rules/alerts`) | - Do not migrate until you have removed all calls to logs endpoints from your application logic
- Review the [critical considerations](/using-the-api/webhooks/migration-guide-advanced#event-log-endpoints) | +| ...`RuleId` in my application's existing logic | - Do not migrate until you have removed all application logic using the `RuleId` property
- Review the [critical considerations](/using-the-api/webhooks/migration-guide-advanced#ruleid-in-existing-logic) | +| ...only company-agnostic webhook functionality | - Request to migrate to the new webhook service
| +| ...company-specific webhook functionality | - Request to migrate to the new webhook service
- Review the [additional considerations](/using-the-api/webhooks/migration-guide-advanced#company-specific-webhooks) | +| ...`X-Codat-ClientId` header to determine the source Codat instance of the event | - Request to migrate to the new webhook service
- Configure a custom header, as described in [additional considerations](/using-the-api/webhooks/migration-guide-advanced#source-client-header) | +| ...webhook auth header via the `/profile` endpoint | - Request to migrate to the new webhook service
- Configure a custom header using the Portal, as described in [additional considerations](/using-the-api/webhooks/migration-guide-advanced#webhook-auth-header) | +| ...webhook auth header via the Portal | - Request to migrate to the new webhook service
- Configure a custom header using the Portal, as described in [additional considerations](/using-the-api/webhooks/migration-guide-advanced#webhook-auth-header) | +| ...`Retry-After` header to control the time between retries | - Request to migrate to the new webhook service
- Review the [additional considerations](/using-the-api/webhooks/migration-guide-advanced#retry-after-header) | ## Critical considerations