customerio-common-errors

name	customerio-common-errors
description	Diagnose and fix Customer.io common errors. Use when troubleshooting API errors, delivery failures, campaign issues, or SDK exceptions. Trigger: "customer.io error", "customer.io not working", "debug customer.io", "customer.io 401", "customer.io 429".
allowed-tools	Read, Grep, Bash(curl:*), Bash(npx:*)
version	1.14.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","customer-io","debugging","errors"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

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)

// WRONG — mixing up API key types
import { TrackClient, APIClient, RegionUS } from "customerio-node";


 cio =  (siteId, trackApiKey, { :  });


 api =  (appApiKey, { :  });