As a reminder, we will turn phone column validations back on starting December 1st, 2022!

Please ensure that your phone numbers follow the appropriate format to avoid errors and losing data. You can find examples to help you structure your numbers correctly in the phone column doc.

We recently made bug fixes that impact the items_by_column_values object:

• The list returned using the created_at field will appear in reverse chronological order, with the most recent dates first.
• Using pagination, you can return 1,000 items per page and 10,000 items overall. Any queries above these limits will fail. For example, a query with a limit of 1,000 that tries to return 11 pages of results will fail (1,000 * 11 = 11,000).

You can now update the people column with an email address by sending a string with the column's new value. Check out the code sample below!

mutation {
  change_simple_column_value(item_id: 123456789, board_id: 987654321, column_id: "person", value: "[email protected]") {
    id
  }
}

We've added four new fields to the workspaces object:

• settings returns the workspaces settings
• owners_subscribers returns the workspaces owner's
• team_subscribers returns the teams subscribed to the workspace
• users_subscribers returns the users subscribed to the workspace

Check out our workspaces doc to find out more!

We recently added the workspace_ids argument to the boards object that filters boards within the specified workspace(s). Read more about the workspace_ids argument in our boards doc!

Last week, we started validating inputs on the phone column. Many of our devs faced issues, so we have temporarily shut off the phone column validation to give extra time to adjust to the change.

We will turn the validation back on beginning December 1st, 2022. The API will then validate whether or not the phone number is valid, includes a 2-letter country code, and matches the specified country code's number criteria.

You can refer to our phone column doc to see up-to-date examples! Please follow this structure to avoid losing data and errors starting December 1st.

We've recently made bug fixes that strictly validate column values in the API. Sending unexpected or invalid values will return an error.

The bug fixes will impact the following columns:

• Country column: The API will now strictly validate the country name.
• Dependency column: The API will now only accept valid item IDs.
• Dropdown column: The API value will now be case-sensitive.
• Long text column: The API will have a hard limit of 2,000 characters.
• Number column: The API will accept negative numbers.
• People column: The API will now validate whether or not the input ID is a valid person or team.

To avoid errors, ensure you don't have any typos and follow these new validation fixes!

We've made three changes to add more actions to the workspaces object, including a new field and mutation!

1. You can now query the workspaces object, rather than nesting it within a boards query.
2. You can also use the new created_at field to return the creation date of a workspace.
3. Lastly, we've added a new mutation that allows you to delete a workspace.

You can find all of the details about these updates and functionality updates in our workspaces doc!

Hello everyone!

Starting April 27th 2023, the users query will work with a page argument when a limit is provided. If the page argument is not provided, it will default to page: 1. This will work in the same way as it does today with the boards or items queries.

Hello everyone!

There has been a change in the complexity points usage for the teams object.

In the past, the complexity usage for teams was working as if each query was retrieving information from only one team.

The complexity is now based on the amount of teams that are queried. If IDs are not provided, the query will assume that there are 1000 teams, each with 1000 users being retrieved.

We suggest using the IDs of the different teams in your queries if you are running into complexity points usage issues. You can use one query to get your teams’ IDs and a second one to query for data from those teams, using the IDs as a parameter.