Skip to main content

HTTP Status Codes

CodeMeaningDescription
200OKRequest succeeded
400Bad RequestMissing or invalid parameters
401UnauthorizedMissing or invalid API key
403ForbiddenAPI key doesn’t have permission for this action
404Not FoundEndpoint doesn’t exist or user not found
429Too Many RequestsRate limit exceeded — wait and retry
500Internal Server ErrorServer-side error — retry with backoff
503Service UnavailableServer temporarily overloaded

Error Response Format

All errors return a JSON body with status_code and message:
{
  "status_code": 401,
  "message": "Invalid or expired API key"
}

Common Errors

Invalid API Key

{
  "status_code": 401,
  "message": "Invalid API key. Get a free key at https://tik.tools"
}
Fix: Check your API key in the Dashboard. Ensure you’re passing it as apiKey query parameter.

User Not Live

{
  "status_code": 400,
  "message": "User is not currently live"
}
Fix: Use /webcast/check_alive to verify the user is live before connecting.

Rate Limit Exceeded

{
  "status_code": 429,
  "message": "Rate limit exceeded. Retry after 60 seconds."
}
Fix: Implement exponential backoff. Check X-RateLimit-Remaining headers to avoid hitting limits. Consider upgrading your tier.

Connection Limit

{
  "status_code": 403,
  "message": "WebSocket connection limit reached for your tier"
}
Fix: Close unused WebSocket connections. Upgrade to a higher tier for more concurrent connections.

WebSocket Close Codes

For WebSocket-specific error codes, see WebSocket Close Codes.