SuprSend uses standard HTTP response codes to indicate the success or failure of your API requests. This page covers common error codes and how to handle them.

​
Success Codes

CodeDescription
200OK - Request succeeded
201Created - Resource was successfully created
204No Content - Request succeeded but no content returned

​
Error Codes

CodeDescription
400Bad Request - Invalid request syntax or parameters
401Unauthorized - Authentication required or failed
404Not Found - Resource not found
5xxInternal Server Error - Unexpected server error

​
Error Response Format

All error responses follow a consistent format: 
{
  "code": 400,
  "error_code": "validation_error",
  "type": "ValidationError",
  "message": "Invalid request parameters",
  "detail": "The 'name' field is required"
}
FieldTypeDescription
codeintegerHTTP status code
error_codestringMachine-readable error identifier
typestringError type classification
messagestringHuman-readable error message
detailstringAdditional error details (optional)

​
Common Error Codes and their solutions

​
401 Unauthorized - authentication_failed

Causes:
  • Missing or invalid service token
  • Expired service token
  • Using environment API key instead of service token
Correct Syntax to authorizate Management API: 
# Ensure you're using a valid service token
curl -H "Authorization: ServiceToken YOUR_SERVICE_TOKEN" \
     https://api.suprsend.com/v1/workflows

​
400 Bad Request - validation_error

Common Causes:
  • Missing required fields
  • Invalid field formats
  • Invalid enum values
Example: 
{
  "code": 400,
  "error_code": "validation_error",
  "type": "ValidationError",
  "message": "Invalid request parameters",
  "detail": "The 'name' field is required and cannot be empty"
}

​
404 Not Found

Common Causes:
  • Given entity in the request is not found
Example: 
{
  "code": 404,
  "error_code": "not_found",
  "type": "NotFound",
  "message": "Workflow not found",
  "detail": "Workflow with slug 'welcome-sequence' does not exist"
}