🏷️ API version: 2025-10

You can now use the board_updates_only argument when querying the updates field inside a boards query. This argument filters the results to return only updates posted directly on the board, excluding item-level updates.

query {
  board (ids: 1234567890) {
    updates (limit: 50, board_updates_only: true) {
      body
      id
      created_at
      creator {
        name
        id
      }
    }
  }
}
🏷️ API version: 2025-10

We added two new arguments to the create_update mutation:

  • original_creation_date: The update's original creation date. Useful in scenarios like account recovery where preserving the original creation date is necessary.
  • use_app_info: Whether to use the app's details as the creator of the update.
mutation {
  create_update (item_id: 9876543210, body: "This update will mention user 1234567890 on an item", mentions_list: [{id: 1234567890, type: User}], use_app_info: true, original_creation_date: "01-03-2025") {
    id
  }
}
🏷️ API version: 2025-10

You can now filter replies queries by board IDs, pages, and creation time ranges using the following arguments:

  • board_ids
  • created_at_from
  • created_at_to
  • limit
  • page
query {
  replies(board_ids: [1234567890], created_at_to: "2025-08-02", created_at_from: "2025-01-01") {
    body
    created_at
    edited_at
    creator {
      id
      name
    }
  }
}
🏷️ API version: 2025-10

We added new fields to the views query to return data about the view's filters, sort, settings, and tags:

  • filter
  • filter_team_id
  • filter_user_id
  • settings
  • sort
  • tags
query {
  boards (ids: 1234567890) {
    views {
      filter
      tags
      settings
      name
      id
    }
  }
}
🏷️ API version: 2025-10

You can now update a folder's position, workspace, or product using the following new arguments on the update_folder mutation:

  • account_product_id
  • position
  • workspace_id
mutation {
  update_folder (
    folder_id: 1234567890,
    name: "Updated folder name",
    account_product_id: 54321,
    position: {
      object_id: "15",
      object_type: Board,
      is_after: false
    }
  ) {
    id
    name
  }
}
🏷️ API version: 2025-10

You can now update a board's position, workspace, or product using the new update_board_hierarchy mutation.

mutation {
  update_board_hierarchy(
    board_id: 1234567890,
    attributes: {
      account_product_id: 54321
      workspace_id: 12345
      folder_id: 9876543210
      position: {
        object_id: "15",
        object_type: Overview,
        is_after: true
      }
    }
  ) {
    success
  }
}
🏷️ API version: 2025-10

You can now change the account product a workspace is in using the new account_product_id field on the update_workspace mutation.

mutation {
  update_workspace (id: 1234567, attributes: { account_product_id: 98765, name:"Marketing team", description: "This workspace is for the marketing team." }) {
    id
  }
}
🏷️ API version: 2025-10

You can now change an item's position on the same board using the new change_item_position mutation. The following example moves 1234567890 after item 9876543210.

mutation { 
 change_item_position (
  item_id: 1234567890,
  relative_to: 9876543210,
  position_relative_method: after_at
 ) {
  id
  group {
   id
  }
 }
}