Error Responses
Understanding error codes and troubleshooting common issues with Tuesday APIs
Overview
The Tuesday Leads API use standard HTTP status codes to indicate the success or failure of API requests. When an error occurs, the response will include a structured error message to help you understand and resolve the issue.
Error Response Format
All error responses follow this consistent structure:
Common Error Codes
400 - Bad Request
Invalid or missing required parameters in your request.
401 - Unauthorized
Invalid or missing API key in request headers.
402 - Insufficient Credits
Not enough credits available to complete the request.
404 - Not Found
The requested resource could not be found.
429 - Rate Limit Exceeded
Too many requests within the allowed time window.
500 - Internal Server Error
Something went wrong on our end. Try again later.
Detailed Error Examples
400 Bad Request
Missing Required Parameter:
Invalid Parameter Format:
Invalid Parameter Value:
401 Unauthorized
Missing API Key:
Invalid API Key:
402 Insufficient Credits
404 Not Found
Resource Not Found:
Endpoint Not Found:
429 Rate Limit Exceeded
500 Internal Server Error
Error Handling Best Practices
1. Always Check Status Codes
2. Implement Retry Logic for Transient Errors
For 429 (rate limits) and 5xx (server errors), implement exponential backoff:
3. Log Errors for Debugging
Troubleshooting Common Issues
Authentication Problems
Authentication Problems
Symptoms: Getting 401 Unauthorized errors
Solutions:
- Verify your API key is correct and properly included in the
X-API-KEY
header - Check that your API key hasn’t expired or been revoked
- Ensure you’re not accidentally including extra spaces or characters
- Generate a new API key if needed
Rate Limiting Issues
Rate Limiting Issues
Symptoms: Getting 429 Rate Limit Exceeded errors
Solutions:
- Implement request throttling in your application
- Use exponential backoff for retries
- Consider upgrading your plan for higher limits
- Distribute requests over time rather than in bursts
Credit Exhaustion
Credit Exhaustion
Symptoms: Getting 402 Insufficient Credits errors
Solutions:
- Check your credit balance in the Tuesday dashboard
- Only request enrichment data when necessary
- Consider upgrading your plan
- Implement credit usage monitoring
Invalid Parameters
Invalid Parameters
Symptoms: Getting 400 Bad Request errors
Solutions:
- Verify all required parameters are included
- Check parameter formats (especially LinkedIn URLs)
- Ensure enum values are correct (e.g., “include” not “true”)
- Review the API documentation for correct parameter names
Data Not Found
Data Not Found
Symptoms: Getting 404 Not Found errors
Solutions:
- Verify the LinkedIn URL is publicly accessible
- Check that the profile or company exists
- Ensure URLs are properly encoded
- Try alternative identifiers if available
Getting Help
If you’re experiencing persistent errors or need additional assistance: