Refer to the article to troubleshoot any issues you encounter.
Code | Cause | Resolution |
---|---|---|
400 Bad Request | - Missing required parameters - Invalid step ID or instance ID - Incorrect data format - Authentication token issues - Attempting to complete already completed steps | - Validate all required fields are present - Ensure IDs are current and valid - Check data formatting matches API specifications - Verify that authentication headers are properly formatted - Query step status before attempting completion |
401 Unauthorized | - Invalid or expired API token - Token lacks necessary permissions - Incorrect token format in headers | - Regenerate API tokens - Verify token permissions match required operations - Ensure proper header format. For example, for Next Matter it’s Authorization: Api-Key {key} |
404 Not found | - Instance or step doesn’t exist - Instance has been deleted - Incorrect API endpoint URL | - Verify instance/step IDs before API calls - Check if instance hasn’t been deleted - Confirm API endpoint URLs match documentation |
429 Too many requests | - Exceeded rate limits | - Distribute requests over time (fewer than 3000 requests per hour) |
500 Internal server error | - Server-side issues - Timeouts on complex operations | - Check system status page and report to support |
504 Gateway timeout | - May happen when filtering large datasets | We have a 60-second timeout limit on all API endpoints. - Use date range filters to limit data scope |