klaviyo-upgrade-migration

# Klaviyo Upgrade & Migration ## Overview Guide for upgrading the `klaviyo-api` SDK, migrating from legacy v1/v2 APIs, and handling breaking changes between Klaviyo API revisions. ## Prerequisites - Current Klaviyo SDK installed - Git for version control - Test suite available ## Klaviyo API Revision Timeline Each revision is supported for **2 years** after release. Connect to the latest every 12-18 months. | Revision | Released | Deprecated | Key Changes | |----------|----------|------------|-------------| | `2024-10-15` | Oct 2024 | Oct 2026 | Reporting API, campaign message updates | | `2024-07-15` | Jul 2024 | Jul 2026 | Custom objects, tracking settings | | `2024-02-15` | Feb 2024 | Feb 2026 | Bulk operations, segments V2 | | `2023-12-15` | Dec 2023 | Dec 2025 | Profile subscription changes | | `2023-07-15` | Jul 2023 | Jul 2025 | Relationship endpoint restructuring | ## Instructions ### Step 1: Assess Current State ```bash # Check current SDK version npm list klaviyo-api # e.g., klaviyo-api@15.0.0 # Check latest available npm view klaviyo-api version # e.g., 21.0.0 # See all available versions npm view klaviyo-api versions --json | tail -10 ``` ### Step 2: Review Breaking Changes ```bash # View changelog # https://github.com/klaviyo/klaviyo-api-node/releases # Find your usage patterns that may be affected grep -rn "from 'klaviyo-api'" src/ grep -rn "ApiKeySession\|ProfilesApi\|EventsApi" src/ ``` ### Step 3: Common Migration Patterns #### Legacy v1/v2 t...