Error Handling - Unifically

Response Structure

All Unifically API responses follow a consistent structure:

Success Response

{
  "success": true,
  "code": 200,
  "data": {
    // Response data
  }
}

Error Response

{
  "success": false,
  "code": 400,
  "data": {
    "message": "Error message"
  }
}

Empty arrays and objects are omitted from responses when not needed.

HTTP Status Codes

Code	Meaning	Description
`200`	Success	Task successfully submitted
`400`	Bad Request	Task generation failed
`401`	Unauthorized	Invalid or missing API key
`422`	Validation Error	Invalid request parameters
`429`	Too Many Requests	Rate limit exceeded
`500`	Internal Server Error	Server error occurred

Error Response Format

When an error occurs, the API returns a simplified structure:

{
  "success": false,
  "code": 400,
  "data": {
    "message": "Error message"
  }
}

Response Fields

boolean

Indicates whether the request was successful (true) or failed (false)

integer

HTTP status code (200, 400, 401, 422, 429, 500)

object

Response data or error details

string

Human-readable error message (on error)

Example Error Responses

Authentication Failed (401)

{
  "success": false,
  "code": 401,
  "data": {
    "message": "Invalid API key provided"
  }
}

Solution: Verify your API key is correct and properly formatted in the Authorization header:

Authorization: Bearer YOUR_ACTUAL_API_KEY

Rate Limit Exceeded (429)

{
  "success": false,
  "code": 429,
  "data": {
    "message": "Rate limit exceeded. Please try again later"
  }
}

Solution: Implement exponential backoff and respect rate limits

Validation Error (422)

{
  "success": false,
  "code": 422,
  "data": {
    "message": "Missing required parameter: prompt"
  }
}

Solution: Check the API documentation for required parameters and valid values

Generation Failed (400)

{
  "success": false,
  "code": 400,
  "data": {
    "message": "Task generation failed"
  }
}

Solution: Review your request parameters and try again

Server Error (500)

{
  "success": false,
  "code": 500,
  "data": {
    "message": "Internal server error occurred"
  }
}

Solution: Retry the request after a brief delay. Contact support if the issue persists

Best Practices

Always Check Success Field

Check the success field in every response to determine success or failure

Implement Retry Logic

Retry failed requests with exponential backoff for 429 and 500 errors

Log Errors

Log all error responses including the error message for debugging

Handle Rate Limits

Implement rate limit handling to avoid 429 errors

Always parse the error.message field to provide helpful feedback to your users

Never expose your API key in client-side code or public repositories

​Response Structure

​Success Response

​Error Response

​HTTP Status Codes

​Error Response Format

​Response Fields

​Example Error Responses

​Best Practices

Always Check Success Field

Implement Retry Logic

Log Errors

Handle Rate Limits

Response Structure

Success Response

Error Response

HTTP Status Codes

Error Response Format

Response Fields

Example Error Responses

Best Practices