We recently updated our API playground to provide a more intuitive and seamless user experience. This update includes a completely revamped UI, tabs that allow you to open multiple sessions at once, HTTP header support, and history tracking.

Currently, you can only access the new playground through the Developer's Center, but we plan to upgrade the public playground in the next few weeks. Check it out for yourself!

Starting April 15th, 2023, we will deprecate connections from Windows Server 2012 R2, Windows 8.1, or earlier because they use weak ciphers. This update will not impact support for TLS 1.3.

Check out this document to find out which systems this update impacts, how to know if you are affected, and which ciphers you can use!

We recently fixed a bug that now allows you to clear a dropdown column by sending an empty array in one of the following mutations:

mutation {
  change_multiple_column_values (item_id: 123456789, board_id: 987654321, column_values: "{\"dropdown\":{\"ids\":[]}}") {
    column_values (ids: dropdown) {
      id
      value
    }
  }
}

mutation {
  change_multiple_column_values (item_id: 123456789, board_id: 987654321, column_values: "{\"dropdown\":{\"labels\":[]}}") {
    column_values (ids: dropdown) {
      id
      value
    }
  }
}

We recently added subitem support for update_column_value and create_pulse activity log queries. Each event has both the parent_board_id and parent_item_id properties. This change will not be applied retroactively, but all events moving forward will contain this information.

You can now return an account's non-active users with the non_active argument. Check out our documentation to learn more!

Today marks a huge milestone as we release the ability to build apps inside workdocs! As part of this release, we have a new set of queries and mutations to read and update workdocs via the API.

You can now query the content of a workdoc and its blocks, create new blocks inside a workdoc, update existing ones, or delete blocks. Check out our workdocs and document blocks documentation to find more details about these new queries and mutations.

You can also check out our developer blog for the full announcement or read through our workdocs app documentation to do a deep dive into the feature and build your first app!

We recently added the position argument or attribute to the update_group and create_group mutations. This new addition allows you to create a group with a specific position or update a group's position using a string that contains a numeric value. The higher the number, the lower the group sits; the lower the number, the higher the group sits.

Starting February 13th, if you create a column via the API with a title of 20 characters or less, the column ID will relate to the title. For example, if your column title is This is my column, then the column ID will be this_is_my_column.

If your title is more than 20 characters, the system will randomly generate a column ID based on the column_type and an ongoing index. It will not be related to the column title.

This update will only impact new columns, not existing ones!

We recently fixed unexpected API behavior that returned all users after running a teams query with an empty array for the ids argument. Now, if you send an empty array, it will return no users.

query {
  teams (ids:[]) {
    id
  }
}

Starting April 15th, 2023, we will deprecate connections from Windows Server 2012 R2, Windows 8.1, or earlier because they use weak ciphers. This update will not impact support for TLS 1.3.

Check out this document to find out which systems this update impacts, how to know if you are affected, and which ciphers you can use!