We have aligned our API for the webhook events: 

• create_subitem
• delete_subitem
• archive_subitem

They now return itemId and pulseId when the event is triggered.

In one week, you will see a descriptive error when you try to add a user to a person column when the user is not assigned to the board.

Previously, this would result in a nonspecific 500 error.

In one week, providing a nonexistent board in a “items_by_column_values” query will result in a 500 error.

In one week, sending an invalid user ID in a create_notification mutation will result in a 500 error.

A valid user ID must be an integer.

The items query is changing to return no items when the limit is set to 0.

Below is an example of the items query with a limit of 0:

query {
  boards {
      items (limit: 0) {
        id
    }
  }
}

The query above will return no items.

Previously, a limit of 0 in an items query would return all items across an account.

Happy building!

You can now retrieve the type of the boards using the type field!

There are three different board types:

• Board (Parent board)
• Sub Items board
• Document

{
  boards(ids:1234567890){
    type
  }
}

{
  "data": {
    "boards": [
      {
        "type": "board"
      }
    ]
  },
  "account_id": 1111111
}

{
  boards(ids:1234567890){
    type
  }
}

{
  "data": {
    "boards": [
      {
        "type": "sub_items_board"
      }
    ]
  },
  "account_id": 1111111
}

{
  boards(ids:1234567890){
    type
  }
}

{
  "data": {
    "boards": [
      {
        "type": "document"
      }
    ]
  },
  "account_id": 1111111
}

You can now query for a user's language via the API!

A user's language can be obtained with a query like this:

query {
    users (ids: [123456789]) {
    		name
     		current_language
    }
}

You can expect a response like this from the query above:

{
  "data": {
    "users": [
      {
        "name": "John Appleseed",
        "current_language": "en"
      }
    ]
  },
  "account_id": 123456789
}

Happy building!

You can now retrieve an item’s email address via the API!

The 'items' query will now accept an 'email' field. Here is an example of a query for an item's email address:

query {
  boards (ids: 12345678) {
    items {
      id
      email
    }
  }
}

The query above will result in a response like this:

{
  "data": {
    "boards": [
      {
        "items": [
          {
            "id": "1234567899",
            "email": "[email protected]"
          }
        ]
      }
    ]
  },
  "account_id": 1234567898
}

Happy building!

You can now delete your board via the API by using the delete board mutation!

Enjoy the ease in deleting boards without the manual work of navigating the site.

The delete board mutation will allow you to delete one board at a time.

Below are examples of how to use this new mutation:

mutation {
    delete_board (board_id: 12345678) {
        id
    }
}

let query = 'mutation { delete_board (board_id: 12345678) { id }}';

fetch ("https://api.monday.com/v2", {
  method: 'post',
  headers: {
    'Content-Type': 'application/json',
    'Authorization' : 'YOUR_API_KEY_HERE'
   },
   body: JSON.stringify({
     'query' : query
   })
  })
   .then(res => res.json())
   .then(res => console.log(JSON.stringify(res, null, 2)));

curl --location --request POST 'https://api.monday.com/v2' \
--header 'Authorization: YourSuperSecretApiKey' \
--header 'Content-Type: application/json' \
--data-raw '{"query": "mutation { delete_board (board_id: 12345678) { id }}"}'

The delete board mutation is currently live and ready for use!

From October 11th, 2022, we'll be validating the JSON you send to update column values. Sending unexpected values will return an error. For example:

To update an hour column, you must send the hour and minute in 24-hour format.

"{\"hour\":16,\"minute\":42}"

If you send an unexpected value, for example:

"{\"hour\":false}"

You will see an error saying that "hour" should be a number and that the "minute" key is missing.

Validation will not only check for expected keys, but for types as well. Sending a string when an integer is expected will result in an error, for example.

How should I respond to this change?

If you are updating column values, you should confirm you are sending expected values by comparing them to our Column Types Reference here: https://api.developer.monday.com/docs/guide-to-changing-column-data