This is a reminder that starting October 18th, 2022, we'll be adding new limits to the root Items query:

  • The ids argument is now required
  • You cannot return more than 100 items per query

This change will go into effect on Tuesday, October 18th, so please review your applications' API usage to prevent any loss of functionality.

We recently added a rate limit to this use case, so you may have already adjusted your code to account for this!

We will remove references to this feature in our docs, but if you spot a mention that we missed shoot us a message at [email protected].

Examples of unsupported queries

Queries without the ids argument:

query {
  items (limit:1000) {
    id
    name
  }
}

Queries with more than 100 IDs:

query {
  items (ids:[1, 2, 3, 4, 5...99, 100, 101, 102]) {
    id
    name
  }
}

How should I respond to this change?

You can adjust your queries in these main ways:

  • Return items on a specific board only
  • Nesting the items query inside Boards
  • Looping through the boards on your account
  • Query less than 100 items at a time

Return items on a specific board

You can return items only on a specific board, by ID. Here's an example:

query {
  boards (ids:12345) {
    id
    name
    items (limit:100) {
      id
      name
    }
  }
}

Nesting the items query inside Boards

Queries without Items in the root will still work, so you can nest the items query within a boards query. Here's an example:

query { 
  boards (limit:10) { 
    items (limit:1000) { 
      id 
      name 
    } 
  } 
}

Looping through the boards on your account

If you are looking to return all items across your account, it is best practice to first query for the IDs of all the boards, and then get items a few boards at a time. For example:

First, query for the IDs of all the boards.

query { 
  boards (limit:50) { 
    id
  } 
}

Second, query and loop through each board in the first query.

query { 
   boards (ids: 1234567890) { 
     items (limit:50) { 
       name 
       id 
     } 
   } 
 }

Return less than 100 items at a time

Finally, you can continue to use the same query but restrict the query to a list of item IDs. Here's an example:

query {
  items (ids: [1, 2, 3, 4, 5... 99]) {
    name
		column_values {
			id
			value
		}
	}
}

This is a reminder that starting October 18th, 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

We have some exciting documentation news 🚀

We have moved our documentation to be hosted on developer.monday.com. This change will provide you with a more unified experience when navigating and searching through our API and App Framework documentation.

The old URLs (api.developer.monday.com and apps.developer.monday.com) will no longer work.

Be sure to update your bookmarks accordingly.

If you see any broken links, please let us know at [email protected]!

Happy building ⚒️

We have added a new field, items_count, to the boards query.

This new field will return the number of items on boards across an account or across certain boards if specified in the query.

The items_count field can be called like this:

query {
  boards {
    items_count
  }
}

With this new field, you can enjoy more ease in working with board data, as you will no longer have to do a manual count of items in your account.

🚧

High complexity cost query

Be sure to use the items_count query with caution, as it comes with a high complexity cost. See more on Rate Limiting here.

Happy building! 🛠

Hello monday builder!

We have released a collection of Postman HTTP request examples to help out community 💪

You can find the collection here.

Let us know what you think!

Cheers, Matias

Hello all!

We have some exciting documentation news today 🚀

We have moved our documentation to be hosted on developer.monday.com. This change will provide you with a more unified experience when navigating and searching through our API and App Framework documentation.  After September 17th, the old URLs (api.developer.monday.com and apps.developer.monday.com) will no longer work.

Be sure to update your bookmarks accordingly.

If you see any broken links, please let us know at [email protected]!

Happy building ⚒️

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.