API

Errors and troubleshooting

Diagnose rejected credentials, invalid events, oversized requests, rate limits, processing failures, and missing journey enrollments.

HTTP errors

Status / code	Likely cause	Resolution
400 INVALID_JSON	Malformed JSON body	Serialize JSON and send application/json
400 INVALID_EVENT	Missing or invalid fields	Compare with the endpoint reference and observed schema
400 INVALID_BATCH	Invalid message or batch shape	Validate every message and keep the batch at 500 or fewer
401 UNAUTHORIZED	Missing, wrong, rotated, or inactive credential	Confirm environment and connection, then rotate if needed
413 PAYLOAD_TOO_LARGE	Body exceeds the endpoint limit	Split the batch or remove unneeded properties
429 RATE_LIMITED	Workspace safety limit reached	Honor Retry-After and inspect accidental event loops
503 INGESTION_UNAVAILABLE	Temporary acceptance failure	Retry with backoff and the same messageId

01
Confirm the response
Check received and duplicate counts and retain the batchId in your structured logs.
02
Check connection status
Paused or rotated connections reject new credentials. Make sure you are viewing the same environment that sent the event.
03
Search by message or customer ID
Allow for asynchronous processing, then inspect rejected or failed state and its safe error message.
04
Check identity
Provider events with no resolvable customer are retained for diagnosis but never start a journey.