Error Handling ​

When interacting with the Storeino API, errors are communicated using standard HTTP status codes and a consistent error response format. This helps you quickly identify and resolve issues in your integration.

Error Response Format ​

All error responses return a JSON object with the following structure:

{
  "status": "error",
  "message": "A human-readable description of the error.",
  "errors": {
    "field_name": [
      "Error message related to the field."
    ]
  }
}

• status: Always "error" for failed requests.
• message: A brief description of the error.
• errors: (optional) An object containing field-specific validation errors.

Example Error Responses ​

Validation Error ​

{
  "status": "error",
  "message": "The given data was invalid.",
  "errors": {
    "email": [
      "The email field is required."
    ]
  }
}

Authentication Error ​

{
  "status": "error",
  "message": "Unauthenticated."
}

Not Found Error ​

{
  "status": "error",
  "message": "Resource not found."
}

Common HTTP Status Codes ​

Handling Errors ​

• Always check the HTTP status code and the error message in the response.
• For validation errors (422), inspect the errors object for details about which fields failed.
• For authentication errors (401), ensure your API key or token is valid and included in the request headers.
• If you encounter a 429 error, wait before making more requests.

Need Help? ​

If you need further assistance, please contact our support team at support@storeino.com.