Release notes

Actively supported versions

This document lists the actively supported API versions in reverse chronological order, allowing you to quickly view the latest features, fixes, and changes.

Versions earlier than 2025-04 are deprecated and no longer supported, but we’ve kept them in a Deprecated versions section at the bottom for migration and troubleshooting reference.

2026-10

Breaking changes

  • The User entity migration that started in 2026-07 completes in 2026-10. See the User entity migration guide.
    • The following legacy User fields are removed: photo_original, photo_thumb, photo_thumb_small, photo_tiny, photo_small, is_guest, is_admin, is_view_only, is_pending, enabled, is_verified, join_date, encrypt_api_token, and sign_up_product_kind
    • The kind, newest_first, and non_active arguments on Query.users are removed. Use user_kind, sort, and status instead

2026-07

Breaking changes

These changes typically cause GraphQL validation or execution errors when an integration has not been updated (wrong arguments, invalid input, or over-limit).

  • The User type and Query.users are overhauled in 2026-07 with new fields, types, enums, query arguments, and enforced pagination. See the User entity migration guide for full details and code examples.
    • Query.users emails argument: element type is now non-null ([String!]). Requests that include null inside the emails array fail validation
    • Query.users limit: values above 1000 are rejected with an error (maximum limit is 1000)

Non-breaking changes

  • New create_validation_rule, update_validation_rule, and delete_validation_rule mutations for board validation rules (see Validation rules guide)
  • New create_doc_blocks mutation with structured CreateBlockInput for rich document blocks (see Document blocks V2)
  • New inferred_metadata and manual_metadata fields on the Board type
  • The User type and Query.users gain new fields, types, enums, input types, and arguments. Several legacy fields and arguments are deprecated (scheduled for removal in 2026-10), and a few scalar types change behavior silently. See the User entity migration guide for full details and code examples.
    • New activity_logs field on the User type for querying user-scoped activity log events with cursor-based pagination
    • New fields on the User type: account_id, status, invitation_method, serial_number, is_deleted, photo_url, became_active_at, bb_visitor_id, is_email_confirmed, and user_config
    • New user_configs query to retrieve per-kind user configuration for the account
    • New PhotoUrl and UserConfig types on User
    • New UserStatus, InvitationMethod, UserKindFilter, UsersSortField, and UsersSortDirection enums
    • New UserKindFilterInput and UsersSortInput input types
    • New user_kind, sort, status, and visibility arguments on Query.users
    • The kind, newest_first, and non_active arguments on Query.users are deprecated and scheduled for removal in 2026-10. Use user_kind, sort, and status instead
    • The following User fields are deprecated and scheduled for removal in 2026-10: photo_original, photo_thumb, photo_thumb_small, photo_tiny, photo_small, is_guest, is_admin, is_view_only, is_pending, enabled, is_verified, join_date, encrypt_api_token, and sign_up_product_kind
    • Dangerous change: Query.users without limit now returns only 200 users by default (previously unbounded). Jobs that relied on one call returning the full account roster will silently under-fetch — use explicit limit and page
    • Dangerous change: User.created_at scalar type changed from Date to ISO8601DateTime! (includes a time component; non-null in the schema). Clients that treat the value as date-only may mis-parse or drop information
    • Dangerous change: User.birthday type changed from Date to String (no longer a dedicated Date scalar)
    • Dangerous change: User.utc_hours_diff type changed from Int to Float (fractional hour offsets are possible). Logic that assumes an integer may produce incorrect results even though the query succeeds

2026-04

Breaking changes

Non-breaking changes

  • New create_project mutation
  • New set_item_description_content mutation
  • New create_marketplace_app_discount mutation
  • New feature-level lifecycle event subscriptions APIs
  • New APIs to manage departments
  • New ability to update an item's nickname
  • New search query for cross-entity search across items, boards, and documents
  • New articles query and mutations for Knowledge Base article CRUD and publishing
  • New article_blocks query for paginated article content blocks
  • New knowledge_base_search query for AI-powered knowledge base search
  • New doc_version_history query to retrieve document version snapshots
  • New doc_version_diff query to compare document versions
  • New notetaker query namespace for meeting recordings, transcripts, summaries, and action items
  • New object_relations query and mutations for managing relations (aliases and dependencies) between objects
  • New relations argument on create_object mutation
  • New relations field on Object type
  • New allowed_sequences_to_enroll query and enroll_items_to_sequence mutation for email sequences
  • New tool_events query for MCP tool execution events in automations
  • New ask_developer_docs query for AI-powered developer documentation answers
  • New prompt argument on create_board mutation to generate board structure via AI
  • New query_params argument on workspaces query to filter by account product kind
  • New created_from_board_id and folder fields on Board type
  • New department field on User type
  • New attribution_entity_ref and attribution_entity_type fields on Like type for reaction attribution
  • New app_feature_slug field on Folder type
  • New APP_FEATURE and LISTVIEW values on ExternalWidget enum

2026-01

Non-breaking changes

2025-10

Breaking changes

Non-breaking changes


2025-07

Hotfixes

  • April 28th, 2025: For column value exception errors, the column_type property no longer returns "Column" appended to the column type. Read more here.
  • May 19th, 2025: All API responses now contain a unique request ID. Read more here.

Breaking changes

Non-breaking changes


2025-04

Hotfixes

  • February 18th, 2025: The complexity budget exhausted error format has changed. Read more here.
  • February 24th, 2025: The create_webhook mutation now returns descriptive errors. Read more here.
  • February 24th, 2025: The renewal_date field is no longer required when querying app subscription details. Read more here.
  • February 27th, 2025: We've introduced changes to the subitems query to help increase performance and return consistent results. Read more here.
  • April 28th, 2025: For column value exception errors, the column_type property no longer returns "Column" appended to the column type. Read more here.
  • May 19th, 2025: All API responses now contain a unique request ID. Read more here.

Breaking changes

  • Deprecated: Sending variables as a JSON string
  • Value field now returns null on connect boards, dependency, and subtasks columns

Non-breaking changes


Deprecated versions

This section covers API versions that are deprecated and no longer supported. They are documented here for historical and migration reference only. Review our API versioning policy for upcoming deprecation timelines.

2025-01

Hotfixes

  • February 18th, 2025: The complexity budget exhausted error format has changed. Read more here.
  • February 24th, 2025: The create_webhook mutation now returns descriptive errors. Read more here.
  • February 24th, 2025: The renewal_date field is no longer required when querying app subscription details. Read more here.
  • February 27th, 2025: We've introduced changes to the subitems query to help increase performance and return consistent results. Read more here.
  • April 28th, 2025: For column value exception errors, the column_type property no longer returns "Column" appended to the column type. Read more here.
  • May 19th, 2025: All API responses now contain a unique request ID. Read more here.

Breaking changes

Non-breaking changes


2024-10

Hotfixes

  • October 22nd, 2024: The item_id argument on the pin_to_top and unpin_from_top mutations has changed from type Int to ID and is no longer required. Read more here.
  • November 6th, 2024: We made version 2024-10backward compatible to resolve parsing errors. Read more here.
  • November 19th, 2024: Updates should be returned in reverse chronological order instead of chronological order. Read more here.
  • February 24th, 2025: The create_webhook mutation now returns descriptive errors. Read more here.
  • February 27th, 2025: We've introduced changes to the subitems query to help increase performance and return consistent results. Read more here.
  • April 28th, 2025: For column value exception errors, the column_type property no longer returns "Column" appended to the column type. Read more here.
  • May 19th, 2025: All API responses now contain a unique request ID. Read more here.

Non-breaking changes


2024-07

Hotfixes

  • April 1st, 2024: You can now filter the date column with multiple exact dates. Check out the full announcement here.
  • May 1st, 2024: Changes to the ComplexityException error structure and error code were reverted. Read more here.
  • May 9th, 2024: The addition of the data object to error codes has been rolled back until version 2025-01. Read more here.
  • May 14th, 2024: Changes to the ComplexityException error message were reverted. Read more here.
  • June 19th, 2024: New descriptive JSON parse error added to all API versions. Read more here.
  • June 20th, 2024: You can now use the add_teams_to_board mutation to subscribe everyone in an account to a board. Check out the full announcement here.

Non-breaking changes

2024-04

Hotfixes

  • March 26th, 2024: Mutations with the column_values argument now accept both string and integer IDs. Check out the full announcement here.
  • April 1st, 2024: You can now filter the date column with multiple exact dates. Check out the full announcement here.
  • May 1st, 2024: Changes to the ComplexityException error structure, error code, and error message were reverted. Read more here.
  • May 14th, 2024: Changes to the ComplexityException error message were reverted. Read more here.
  • June 19th, 2024: New descriptive JSON parse error added to all API versions. Read more here.
  • June 20th, 2024: You can now use the add_teams_to_board mutation to subscribe everyone in an account to a board. Check out the full announcement here.

Breaking changes

  • New kind field accepted enum values on version and versions queries
  • Updated field types on app_installs queries

Non-breaking changes

2024-01

Hotfixes

  • March 26th, 2024: Mutations with the column_values argument now accept both string and integer IDs. Check out the full announcement here.
  • May 1st, 2024: Changes to the ComplexityException error structure, error code, and error message were reverted. Read more here.
  • May 14th, 2024: Changes to the ComplexityException error message were reverted. Read more here.
  • June 19th, 2024: New descriptive JSON parse error added to all API versions. Read more here.
  • June 20th, 2024: You can now use the add_teams_to_board mutation to subscribe everyone in an account to a board. Check out the full announcement here.

Breaking changes

Non-breaking changes

2023-10

Hotfixes

  • December 3rd, 2023: We aligned the empty value results for the text field when querying through column_values V2 to the behavior seen in version 2023-07. Check out the full announcement here.
  • March 26th, 2024: Mutations with the column_values argument now accept both string and integer IDs. Check out the full announcement here.
  • June 19th, 2024: New descriptive JSON parse error added to all API versions. Read more here.
  • June 20th, 2024: You can now use the add_teams_to_board mutation to subscribe everyone in an account to a board. Check out the full announcement here.

Breaking changes

  • Removed the deprecated items field on boards queries, replaced it with items_page

  • Removed the deprecated items field on groups queries, replaced it with items_page

  • New column values fields and typed column values

  • Removed the deprecated items_by_column_values and items_by_multiple_column_values objects, replaced them with items_page_by_column_values

  • The column_type field on the create_column mutation is now required

  • Empty parentheses are no longer supported

  • Quotation marks for strings are now required

  • Removed the deprecated pos fields on boards and columns queries

  • Column type strings have changed. The type field on columns queries has changed from String! to ColumnType!

  • Deprecated the newest_first argument on boards queries

  • Many of the ID arguments and fields have changed from Int to ID type

  • Text field returns empty results for mirror, dependency, and connect boards columns when querying through column_values or the specific MirrorValue, DependencyValue and BoardRelationValue types. Use the display_value field instead.

Non-breaking changes