You can now retrieve a board's muted notification settings via the API by querying the mute_board_settings object. It returns the muted notification state for one or more boards.
query {
mute_board_settings (board_ids: 1234567890) {
board_id
mute_state
}
}{
"data": {
"mute_board_settings": [
{
"board_id": "1234567890",
"mute_state": "CURRENT_USER_MUTE_ALL"
}
]
},
"extensions": {
"request_id": "YOUR_REQUEST_ID"
}
}The API now supports creating, updating, and deleting Workforms and their components using the following new mutations:
- Create form
- Create form question
- Create form tag
- Activate form
- Update form
- Update form question
- Update form settings
- Update form tag
- Set form password
- Shorten form URL
- Deactivate form
- Delete question
- Delete form tag
You can now use the connect_project_to_portfolio mutation to connect an existing project board to a portfolio board via the API. This mutation is part of a monday.com portfolio solution and only available on Enterprise plans.
mutation {
connect_project_to_portfolio (projectBoardId: 1234567890, portfolioBoardId: 9876543210) {
portfolio_item_id
request_id
message
success
}
}The new form query lets you read monday.com Workforms via the API. You can retrieve detailed metadata about a form, including its accessibility, appearance, features, questions, and tags.
👉 Learn more in the form reference and other types docs
query {
form(formToken: "b7f92c1a8d4e43c6a91e5f0dbb27f94e") {
id
title
active
appearance {
primaryColor
showProgressBar
}
features {
responseLimit {
enabled
limit
}
}
questions {
id
title
type
}
}
}You can now use the create_portfolio mutation to create a portfolio board as part of a monday.com portfolio solution via the API.
This mutation is available on Enterprise plans only.
mutation {
create_portfolio (
boardName: "New Portfolio Board"
boardPrivacy: "private"
destinationWorkspaceId: 12345,
) {
success
message
solution_live_version_id
}
}On February 15th, 2026, we will start deprecating API versions 2025-01 and 2024-10.
After this date, any calls to these versions will automatically be routed to version 2025-04. This change may cause unexpected behavior or break existing functionality.
To avoid disruptions, update your API calls to version 2025-04 (or later) before this date.
We've prepared a migration guide to help you upgrade to version 2025-04 smoothly.
Have questions? Post them in our developer community.
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
}
}
}
}We added a new argument 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.
mutation {
create_update (item_id: 9876543210, body: "This update will mention user 1234567890 on an item", mentions_list: [{id: 1234567890, type: User}], original_creation_date: "01-03-2025") {
id
}
}