NavoChatDeveloper docs
Troubleshoot API channel errors
Use status codes to locate signing, channel, identity, thread, and payload problems.
Updated 2026-07-24For: Backend developers
Start by recording the HTTP status, response error code, messageId, threadId, and request time. Never log the signing secret or complete sensitive customer data.
Common statuses
| Status | Meaning | Action |
|---|---|---|
| 400 | Invalid field, type, or size | Correct the request; do not retry unchanged |
| 401 | Expired timestamp or invalid signature | Check server time, raw body, and secret |
| 404 | Channel not found | Check environment, host, and channelId |
| 409 | threadId belongs to another customer or state conflict | Correct the external thread mapping |
| 410 | Channel disabled or archived | Restore the channel or stop sending |
| 429 | Rate limit exceeded | Retry with backoff |
| 5xx | Temporary service error | Retry with the same messageId |
Callback failure
Review the latest callback state in channel details and run the test action. Confirm that public HTTPS is reachable, the response completes before timeout, signature verification uses the raw body, and the service does not return a redirect.