klaviyo-common-errors

# Klaviyo Common Errors ## Overview Quick reference for the most common Klaviyo API errors with real error payloads, root causes, and solutions. ## Prerequisites - `klaviyo-api` SDK installed - API credentials configured - Access to application logs ## Instructions ### Step 1: Identify the Error Klaviyo returns JSON:API error responses. Extract the status code and error detail: ```typescript try { await profilesApi.createProfile(payload); } catch (error: any) { console.error('Status:', error.status); console.error('Errors:', JSON.stringify(error.body?.errors, null, 2)); // error.body.errors[] has: { id, code, title, detail, source } } ``` ### Step 2: Match and Fix --- ### 400 -- Bad Request (Validation Error) **Actual Klaviyo response:** ```json { "errors": [{ "id": "abc-123", "code": "invalid", "title": "Invalid input.", "detail": "The email field is required.", "source": { "pointer": "/data/attributes/email" } }] } ``` **Common causes:** - Missing required field (email, metric name, list name) - Invalid phone number format (must be E.164: `+15551234567`) - Invalid filter syntax in query params - Wrong `type` value in JSON:API payload - Sending `snake_case` instead of `camelCase` (SDK uses camelCase) **Fix:** ```typescript // Wrong: snake_case { first_name: 'Jane', phone_number: '+155...' } // Right: camelCase (SDK convention) { firstName: 'Jane', phoneNumber: '+15551234567' } ``` --- ### 401 -- Unauthorized **Actual response...