This Sunday, the API will briefly be read-only for scheduled maintenance. Only accounts in the AU region will be affected. We estimate the maintenance will take less than 5 minutes.

During this time, queries will operate normally, but mutations will return an error. If you receive an error, please retry your API calls after a few minutes.

The maintenance will be at 12 am AEST or 2 pm UTC.

You can subscribe to updates on our status page: Maintenance on May 25th

Enterprise customers can now programmatically create, read, update, and delete managed status and dropdown columns via the API. Learn more here!

query {
  managed_column (state: active) {
    created_by
    revision
    settings {
      ...on StatusColumnSettings { 
        type
        labels {
          id
          description
        }
      }
    }
  }
}

All API responses now contain a unique request ID to help measure performance, track the full request lifecycle across services, and simplify troubleshooting. When debugging issues with our support team, you can share this ID to quickly locate the problem without needing to search through your logs.

{
  "data": {
    "timeline_item": null
  },
  "errors": [
    {
      "message": "User is not allowed to read timelineItem.",
      "locations": [
        {
          "line": 1,
          "column": 2
        }
      ],
      "path": [
        "timeline_item"
      ],
      "extensions": {
        "code": "UNAUTHORIZED"
      }
    }
  ],
  "extensions": {
    "request_id": "152b0dgb-d38c-067c-9f79-dd0c0d7238ed"
  }
}

You can now retrieve an item's description using the new description field on items queries. This field returns the item's ID and content blocks where the description is stored. Check out the example below:

query {
  items(ids: [1234567890]) {
    name
    description {
      id
      blocks {
        id
        content
      }
    }
  }
}

You can now query assets attached to an update’s replies using the new assets field. Learn more about the available fields on the Reply object here.

query {
  items (ids: 1234567890) {
    updates {
      replies {
        assets {
          id
        }
      }
    }
  }
}

ColumnValueException errors return the column_type property to indicate the type of column that caused the error. Previously, this property returned the column type with the word "Column" appended:

For example: "ColorColumn", "StatusColumn", "DateColumn"

After this update, the column_type property now returns just the column type without "Column" appended. You can find the full list of supported column types here.

For example: "color", "status", "date"

Here’s an example of an updated error response:

{
  "message": "invalid value - label does not exist in column. Please check our API documentation for the correct data structure for this column. https://developer.monday.com/api-reference/docs/change-column-values",
  "locations": [
    {
      "line": 1, 
      "column": 10
    }
    ],
  "path": [
    "change_column_value"
    ],
  "extensions": {
    "code": "ColumnValueException", 
    "status_code": 200, 
    "error_data": {
      "column_type": "color", 
    }
  }
}

You can now create a workspace within a specific product by using the new account_product_id argument in the create_workspace mutation.

mutation {
  create_workspace (name:"New Workspace", kind: open, description: "This is a new workspace in the CRM product.", account_product_id: 505616) {
    id
    description
  }
}

You can now create empty boards using the new empty argument on the create_board mutation. When used, this creates a new board without any items in the default group.

mutation {
  create_board (empty:true, workspace_id:123456, board_kind:public, board_name:"New board") {
    id
  }
}

You can now query apps built with the monday.com apps framework using the new app object. This query retrieves metadata about your apps and their features.

You can query it directly at the root or nest it within a platform_api query to retrieve API consumption data for the account's top six apps.

query {
  platform_api {
    daily_analytics {
      by_app {
        app {
          name
          features {
            type
            name
          }
          id
          api_app_id
          state
        }
        usage
      }
    }
  }
}

You can now query your account's daily API consumption using the new platform_api object. This object includes fields that provide insights into your account's daily API call limit, usage, and top contributors.

query {
  platform_api {
    daily_analytics {
      by_day { 
        day
        usage
      }
      by_app {
        app {
          name
        }
        api_app_id
        usage
      }
      by_user {
        user {
          name
        }
        usage
      }
      last_updated
    }
  }
}