customerio-common-errors

# Customer.io Common Errors ## Overview Diagnose and fix the most frequent Customer.io integration errors: API status codes, SDK exceptions, delivery failures, campaign trigger issues, and transactional message problems. ## Prerequisites - Access to Customer.io dashboard - API credentials configured - Access to application logs ## HTTP Status Code Reference | Code | Meaning | Retryable | Action | |------|---------|-----------|--------| | `200` | Success | N/A | No action needed | | `400` | Bad Request | No | Fix request payload — see details below | | `401` | Unauthorized | No | Check API credentials | | `403` | Forbidden | No | API key lacks permission for this endpoint | | `404` | Not Found | No | Check endpoint URL or resource ID | | `408` | Request Timeout | Yes | Retry with backoff | | `422` | Unprocessable Entity | No | Validation error — check required fields | | `429` | Rate Limited | Yes | Back off, respect `Retry-After` header | | `500` | Internal Server Error | Yes | Retry with exponential backoff | | `503` | Service Unavailable | Yes | Check status.customer.io, retry later | ## Instructions ### Error 1: Authentication Failures (401/403) ```typescript // WRONG — mixing up API key types import { TrackClient, APIClient, RegionUS } from "customerio-node"; // Track API uses Site ID + Track API Key (Basic Auth) const cio = new TrackClient(siteId, trackApiKey, { region: RegionUS }); // App API uses App API Key (Bearer Auth) — DIFFERENT key const api = new APIC...