Guides
Apps DocsCommunityNeed Help?

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.

2027-01

🚧

Release candidate. 2027-01 may still change before it becomes the current version on January 15, 2027.

Breaking changes

  • Activity logs:
    • Board.activity_logs returns a BoardActivityLogsPage (logs and cursor) instead of a list of ActivityLogType. Select the entries under logs and read cursor to fetch the next page
    • The page argument is removed. Paginate with the new cursor argument instead
    • The from and to arguments are now String (previously ISO8601DateTime). from can be at most 90 days ago, and requests for older data return a validation error
    • The column_ids and group_ids arguments are now [ID!] (previously [String])
    • The limit argument no longer declares a schema default of 25. It accepts 1–1000 and the documented default is still 25

Non-breaking changes

  • Activity logs:
    • New event_types, correlation_ids, cursor, and search arguments on Board.activity_logs — filter by event type or correlation ID, page with a cursor, and prefix-search item names
  • External agents:
    • New subscribe_users_to_agent and unsubscribe_users_from_agent mutations — subscribe up to 200 users to an agent with an owner or member role, or unsubscribe up to 200 users from it
    • New agents query — retrieve agents and filter their user or team subscribers by type and role
    • New subscribers field on the Agent type — lists the users and teams subscribed to an agent and their owner or member role
    • New EXTERNAL_AGENT_MEMBER and EXTERNAL_AGENT_DETACHED_MEMBER values on BaseRoleName — assign external-agent roles with update_users_role
  • Typed item pages:
    • New root-level items_page query, separate from the nested boards { items_page } field — query a board or data view by ID with filters, hierarchy options, and cursor pagination
    • New typed item results and column values — return groups, linked items, subitems, parent items, metadata, capabilities, and structured values through inline fragments
  • New include_project_board_link input on create_board_export — add a trailing Project Board column with the first linked project board ID to CSV exports, or a blank value when no project is linked; the column is only added on accounts where this capability is enabled
  • New DATA_VIEW source for aggregate — aggregate from a data view ID as well as a table ID

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 remain deprecated; use user_kind, sort, and status instead
  • Workforms:
    • The update_form_tag mutation is removed. Delete and recreate the tag as a replacement. See the Form reference
    • The FormFormat enum type and the format field on FormLayout and FormLayoutInput are removed. Remove references to format and FormFormat before migrating
    • The value field on FormTag and CreateFormTagInput is removed. Remove any queries or inputs that use value on form tags before migrating
    • The UpdateFormTagInput input type is removed (used only by the now-removed update_form_tag mutation)
    • FormQuestion.showIfRules (camelCase) is removed. Use show_if_rules (snake_case) instead

Non-breaking changes

  • Search:
    • New search.users field on the SearchNamespace — search for users by name or email. Returns SearchUserResults with indexed data and optional live data resolution
    • New search.updates field on the SearchNamespace — search for updates by body, board, creator, and date range. Returns SearchUpdateResults with indexed data and optional live data resolution
    • New search.timeline_items field on the SearchNamespace — search Emails & Activities timeline items by title, summary, and content, filtered by board, workspace, item, TimelineItemKind, TimelineItemProductKind, and date range. Returns SearchTimelineItemResults with indexed data and optional live data resolution
    • New search.overviews field on the SearchNamespace — search dashboards by name, workspace, kind, and creator. Returns SearchOverviewResults with indexed data and optional live data resolution
    • New ids argument on search.docs — filters results to up to 512 document IDs; indexed document results now include matched highlights
  • Apps:
    • New promote_app mutation to asynchronously promote a draft app version to live
    • New DeveloperAppVersion type and AppVersionStatus enum for tracking app version promotion status
    • New versions field on App — returns [DeveloperAppVersion!] for polling version promotion status
    • New MCP_SERVER value on AppFeatureTypeE — identifies apps that expose an MCP server feature
    • New retrieval_only argument on ask_developer_docs — returns relevant documentation without an AI-generated summary
  • Workforms:
    • New show_if_rules (snake_case) field on FormQuestion — replaces the removed showIfRules camelCase alias
  • AI:
    • New run_prompt mutation — runs a single prompt against a monday-hosted AI model and returns the generated text. Accepts an optional RunPromptConfigInput (model, system prompt, temperature, max tokens) and returns a RunPromptResult. Requires the External AI gateway access permission (and the AI:Consume scope for apps). A simplified alternative to the Models API; see the AI reference
    • New AI column mutations — configure a column to categorize, summarize, translate, improve text, extract, run an open prompt, write content, or assign people, or remove AI from a column. See the AI Column reference
  • New aggregate_history and items_history queries — retrieve aggregated board data or item data at a specific historical date for point-in-time analysis. When the query references a date column, timestamps before that board's date-column history began are rejected
  • Activity logs:
    • New correlation_ids and entities arguments on User.activity_logs — filter user-scoped activity log events by correlation IDs or related entities
    • New correlation_id, triggering_flow_id, and triggering_flow_type fields on activity-log events — correlate events with logical sessions and triggering flows. See the Activity logs guide
  • Users:
    • New CRM_USER_AGENT_MEMBER and SERVICE_AI_AGENT_MEMBER values on UserKindFilter — filter Query.users by agent kind via user_kind
  • New search_in, start_time_from, and start_time_to arguments on notetaker.meetings — search_in works only alongside search; start_time_from and start_time_to apply only to ranked search, and results include relevance scores and matched content slices
  • New sub_type field on object schema column inputs and output — configure and inspect mirror and lookup column subtypes
  • New kind_names argument on notifications — may be ignored unless an account feature flag is enabled; check kind_name on results; notification results also expose kind and kind_name
  • New consumption field on platform_api.daily_limit — reports the account's consumed daily API limit
  • Templates:
  • Boards:
    • New change_board_kind mutation — changes a board's privacy kind (public, private, or shareable)
    • New update_teams_board_role mutation — updates the board role for one or more teams already subscribed to a board. Returns UpdateTeamsBoardRoleResponse
    • New update_users_board_role mutation — updates the board role for one or more users already subscribed to a board. Returns UpdateUsersBoardRoleResponse
    • New board_automations query and delete_board_automation mutation — list account or board automations with pagination and delete an automation
    • New member value on BoardBasicRoleName — the default board role; can only be used for agent users. update_teams_board_role rejects this value
    • New would_create_mls_rollup_cycle query — checks whether connecting two items would create a multi-level board rollup cycle
    • New use_dataset_template and use_mls_template arguments on create_board — set either to true to create the board from the dataset template or the MLS template; both default to false
  • Board views:
    • New duplicate_view and restore_view mutations on board views
    • New context and conditional_formatting_settings arguments on view mutations — conditional_formatting_settings replaces all existing conditions when supplied, and context sets the view's entity scope (currently only BOARD, the default)
  • Board exports:
    • New create_board_export mutation — exports a board's items to a CSV file. Returns ExportResult, a union of ExportFile (the export finished during the request, so the download URL is ready) and ExportAsyncJob (the export is still running, so poll for it). The server chooses the branch from board size and current load, so select both and switch on __typename. Accepts time_zone to format date values, and an optional CreateBoardExportOptionsInput covering subitems, header format, per-column-type value formatting, and columns_order to select and order the exported columns. Requires the boards:read scope and is only available for Enterprise plans
    • New export_job_status query — polls an asynchronous board export by job_id. Returns ExportJobStatusInfo with an ExportJobStatus, the download URL once the export completes, and an ExportFailureReason if it fails. Requires the boards:read scope and is only available for Enterprise plans
  • New Availability APIs to manage work schedules, company time off, resource assignments, and personal time off (PTO). Includes work_schedules, time_offs, resources_availability, account_availability_defaults, and user_pto queries plus matching create, update, delete, assign, and unassign mutations. See the Availability reference

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)
  • connection_board_ids query: the argument was renamed from connectionId to connection_id (snake_case) and is now required (ID!). The return type also changed from [Int!] to [ID!]!. Update your calls to use connection_id before migrating. See Connect Boards column
  • Board.columns: the capabilities argument no longer has a default value. Callers that previously relied on the implicit default must now pass the argument explicitly

Non-breaking changes

  • New search.workspaces field on the SearchNamespace — search for workspaces by name, kind, and description. Returns SearchWorkspaceResults with indexed data and optional live data resolution
  • New job_status query — polls a general-purpose async job by external ID; returns AsyncJobStatus
  • New cross_product_collaborative argument on set_board_permission mutation — enables cross-product collaboration permissions when set to true
  • Developer Tools:
    • New mcli GraphQL CLI — a single-binary command-line interface for monday.com's GraphQL API with JSON output, semantic business-layer operations, webhook support, and LLM-native design. See the mcli CLI guide.
  • Portfolio:
    • New callback_url argument on create_portfolio mutation — pass an HTTPS URL to receive the new portfolio_id asynchronously; the mutation returns immediately with a process_id, and monday.com POSTs { is_success, process_id, portfolio_id } to your endpoint when the portfolio board is created
    • New process_id field on CreatePortfolioResult type — returned when using callback_url; use for correlating async operations with completion callbacks
  • Workforms:
    • New HOUR, DISPLAY_TEXT, and PAGE_BLOCK values on FormQuestionType enum
    • New optional fields on CreateQuestionInput: show_if_rules, existing_column_id, insert_after_question_id, page_block_id
    • New ai_translate field on FormFeaturesInput, allow_create_item on FormMondayInput, type on FormLayoutInput, is_anonymous on UpdateFormSettingsInput, label_limit_count_enabled and default_answer on FormQuestionSettingsInput, value and visible on QuestionOptionInput, show_if_rules and options on UpdateQuestionInput, page_block_id on QuestionOrderInput
    • New show_if_rules field on FormQuestion (the camelCase alias showIfRules is removed in 2026-10)
  • 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; no removal is scheduled yet. 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

Breaking changes

Non-breaking changes

2025-04

Hotfixes

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

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 about the item_id argument change.
  • November 6th, 2024: We made version 2024-10backward compatible to resolve parsing errors.
  • November 19th, 2024: Updates should be returned in reverse chronological order instead of chronological order. Read more about update ordering.
  • February 24th, 2025: The create_webhook mutation now returns descriptive errors. Read more about descriptive create_webhook errors.
  • February 27th, 2025: We've introduced changes to the subitems query to help increase performance and return consistent results. Read more about the subitems query changes.
  • April 28th, 2025: For column value exception errors, the column_type property no longer returns "Column" appended to the column type. Read more about the column value exception error change.
  • May 19th, 2025: All API responses now contain a unique request ID. Read more about unique request IDs.

Non-breaking changes

2024-07

Hotfixes

Non-breaking changes

2024-04

Hotfixes

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

Breaking changes

Non-breaking changes

2023-10

Hotfixes

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

Updated 2 days ago

Did this page help you?