We recently made a change to our API complexity limits for apps. From now on, read and write actions will be broken into 5 million buckets each.

For more information, check out our community announcement here.

You can now create dependency columns via the API, as well as update their column values. You can find more info on the values this column supports in our Column Types Reference here.

The pos field for columns has now been deprecated. If included in any column queries, the value will be returned null.

Check out our Columns page for more information.

Mirror columns can now be connected to multiple columns on different boards. Therefore, the settings_str for any mirror columns that support this functionality will have a different JSON structure.

If your app uses this data, you must support both JSON formats.

The linked columns will now be stored in the displayed_linked_columns key, instead of the displayed_column key. See below for examples:

Previous format: JSON settings for mirror columns that don't support multi-board mirroring

{
  "relation_column": {
    "link_to_item" : true
  },
  "displayed_column": {
    "timeline": true
  }
}

New format: JSON settings for mirror columns that support multi-board mirroring

{
  "relation_column":{
    "link_to_item":true
  },
  "displayed_column": {},
  "displayed_linked_columns": {
    "101339646": [
      "linked_column_id"
    ]
  }
}

To support both versions, your app should check displayed_linked_columns for a value. If the key does not exist or is blank, then use the value in displayed_column.

To learn more about multi-board mirroring, check out this article: Multi-board mirroring

We released a new field parent_item when querying items that will allow you to see parent item data when querying your subitems.

To learn more, check out our Subitems article and our community announcement,

We now support subscribing to sub-item events with Webhooks. You can use the Integration Center, as well as the API to do so.

Find out more on the Webhooks documentation page, and in this community post.

We released a new items_by_multiple_values method that will allow you to query your items using multiple column values within a single column.

You can learn more in our community post here.

Added mutation-specific rate limits, based on the number of API calls made within a minute for the following mutations:

• duplicate_group;
• duplicate_board;

The mutations above will have an additional rate limit of 40 mutations per minute. If you exceed this limit, you will receive a 429 HTTP response code with "Call limit exceeded for DuplicateGroup" or "Call limit exceeded for DuplicateBoard" error message.

You now have the option to check if a user has confirmed their email profile when querying Users. Use the "is_verified" field, which will return true if the user has already confirmed their profile.

Added support for updating the location column with either simple String values or JSON values. See the location column for more information.