Results

How Meshes API responses use HTTP status codes, and how to interpret error bodies and parameter-level validation details.

Meshes uses standard HTTP status codes to indicate whether a request succeeded or failed.

2XX status codes indicate success.
4XX/5XX status codes indicate an error.

When you receive an error status code, inspect the response body for an error name, a human-readable message, and (when applicable) parameter-level details.

Status Codes

Status Code	Description	Most Likely Cause
200	Successful request	—
201	Successful creation	Returned when a resource is created
204	Successful request	No content returned; request processed successfully
207	Mixed results	Returned when successful and error results are combined
400	Bad request	Invalid or missing data
401	Unauthorized	Invalid or missing credentials
403	Forbidden	Insufficient permissions for the resource
404	Not found	The resource doesn’t exist (invalid or non-existent id)
405	Method not allowed	Invalid HTTP method for the resource
409	Conflict	Resource conflict (e.g., creating a member with an email that already exists)
429	Too many requests	API rate limit exceeded
500	Internal error	Unexpected server error
503	Service unavailable	Service unavailable (commonly during maintenance)

Example Error Message

{
  "message": "Bad Request",
  "error": {
    "name": "BadRequest",
    "message": "Generic error message here"
  }
}

Example Error Message With Details

{
  "message": "Bad Request",
  "error": {
    "name": "BadRequest",
    "message": "Generic error message here",
    "data": [
      {
        "param": "parameter_name",
        "msg": "Specific error message for the parameter"
      }
    ]
  }
}