If your API request cannot be completed successfully, you will receive an error message.

Error format

The error format depends on which version you are using.

Version 2025-01

Starting in version 2025-01, errors returned by the API will have the following characteristics:

• HTTP status: Response will be 200 – OK for application-level errors. Other statuses will be returned for transport-layer errors, such as 500 - Internal server error, 429 - Too many requests or 400 - Bad request
• JSON response: Body will contain an errors array with further details about each error
• Partial data: Requests will return partial data, so the data object may also contain some information. For example, if you query 3 fields, you may get two back and one error.
• Retry-After header: Errors will include the Retry-After header to indicate how long you need to wait before making another request

Sample format

Here's an example of an application-level error:

{
  "data" : [],
  "errors": [
    {
      "message": "User unauthorized to perform action",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "me"
      ],
      "extensions": {
        "code": "UserUnauthorizedException",
        "error_data": {},
        "status_code": 403
      }
    }
  ],
  "account_id": 123456
}

{
  "data": {
    "me": {
      "id": "4012689",
      "photo_thumb": null
    },
    "complexity": {
      "query": 12
    }
  },
  "errors": [
    {
      "message": "Photo unavailable.",
      "locations": [
        {
          "line": 4,
          "column": 5
        }
      ],
      "path": [
        "me",
        "photo_thumb"
       ],
      "extensions": {
        "code": "ASSET_UNAVAILABLE"
      }
    }
  ],
  "account_id": 18888528
}

📘

Developing a new application?

Start with version 2025-01 to take advantage of simplified error responses. Pass a version name with your API calls to enable the unified error format.

Versions 2024-10 and earlier

Versions of the API before 2024-10 return 3 different JSON formats for different errors. These are unified in version 2025-01.

Error format

Check out the tabs below for the different possible formats in 2024-10 (legacy) and 2025-01 (updated).

# Error structure in 2024-10 and earlier
{
  "errors": [
    {
      "message": "Parse error on \")\" (RPAREN) at [59, 15]",
      "locations": [
        {
          "line": 59,
          "column": 15
        }
      ]
    }
  ],
  "account_id": 1234567890
}

# Error structure in 2024-10 and earlier

{
  "errors": [
    {
      "message": "User unauthorized to perform action",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "me"
      ],
      "extensions": {
        "code": "UserUnauthorizedException",
        "error_data": {},
        "status_code": 403
      }
    }
  ],
  "error_message": "User unauthorized to perform action",
  "error_code": "UserUnauthorizedException",
  "error_data": {},
  "status_code": 403,
  "account_id": 123456
}

# Error structure in 2024-10 and earlier

{  
    "error_message": "Internal server error",
    "status_code": 500
}

# Error structure in 2025-01 onwards

{
  "data" : [],
  "errors": [
    {
      "message": "User unauthorized to perform action",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "me"
      ],
      "extensions": {
        "code": "UserUnauthorizedException",
        "error_data": {},
        "status_code": 403
      }
    }
  ],
  "account_id": 123456
}

Errors by status code

2xx errors

Errors with a 2xx status code indicate that monday.com is not accepting the requested action due to a platform platform restriction, limitation, or rule. These errors occur for various reasons, including passing invalid values, missing permissions, or reaching character limits.

Here are some of the most common errors:

4xx client errors

Errors with a 4xx status code indicate that something went wrong on the client's (your) side. These errors occur for various reasons, including not having access to the requested information, using the API at too high a volume, or providing incorrect input.

Here are some of the most common errors:

5xx server errors

Errors with a 5xx status code indicate that something went wrong on the server (monday's) side.

Here are some of the most common errors:

📘

Join our developer community!

We've created a community specifically for our devs where you can search through previous topics to find solutions, ask new questions, hear about new features and updates, and learn tips and tricks from other devs. Come join in on the fun! 😎