In API versions 2025-01 and later, you can update a user's email domain through the API using the new update_email_domain mutation!
mutation {
update_email_domain (input: {new_domain: "[email protected]", user_ids: [123456, 654321]}) {
updated_users {
name
is_admin
}
errors {
user_id
code
message
}
}
}
In API version 2025-01 and later, column validations for apps will be enforced for all columns. Invalid JSON will return a ColumnValueException error code.
In API versions 2025-01 and later, you can remove owners from a team through the API using the new remove_team_owners mutation!
mutation {
remove_team_owners (user_ids: [654321, 123456], team_id: 24681012) {
errors {
message
code
user_id
}
team {
owners {
id
}
}
}
}
In API versions 2025-01 and later, you can owners to a team through the API using the new assign_team_owners mutation!
mutation {
assign_team_owners (user_ids: [654321, 123456], team_id: 24681012) {
errors {
message
code
user_id
}
team {
owners {
id
}
}
}
}
In API versions 2025-01 and later, you can update a user's role through the API using the new update_users_role mutation!
mutation {
update_users_role (user_ids: [12345, 54321], new_role: ADMIN) {
updated_users {
name
is_admin
}
errors {
user_id
code
message
}
}
}
In API versions 2025-01 and later, you can deactivate users through the API using the new deactivate_users mutation!
mutation {
deactivate_users (user_ids: [54321, 12345]) {
deactivated_users {
id
name
}
errors {
message
code
user_id
}
}
}
In API versions 2025-01 and later, you can read the formula column using the display_value field. This field returns the content of the formula column as a string.
This feature is in an early release phase and has the following limitations:
As we do additional testing and development, these limitations will gradually be reduced or removed.
query {
boards(ids: [1234567890]){
items_page(limit:2){
items{
id
column_values {
...on FormulaValue{
display_value
id
type
}
}
}
}
}
}
We recently fixed a bug that caused updates to be returned in chronological order (oldest first) instead of reverse chronological order (newest first) when queried through items. This bug impacted API versions 2024-10 and later.
The fix was deployed, and updates should now be returned in reverse chronological order.
query {
items (ids: 123456890) {
updates {
id
created_at
}
}
}
In version 2025-01, we added two new fields on updates queries:
edited_at: Returns the date the update's body was last editedviewers: Returns data about the update's viewersquery {
updates {
body
edited_at
viewers {
user_id
medium
user {
name
}
}
}
}
let query = "query { updates { body edited_at viewers { user_id medium user { name }}}}";
fetch ("https://api.monday.com/v2", {
method: 'post',
headers: {
'Content-Type': 'application/json',
'Authorization' : 'YOUR_API_KEY_HERE'
},
body: JSON.stringify({
query : query
})
})
.then(res => res.json())
.then(res => console.log(JSON.stringify(res, null, 2)));
In API versions 2025-01 and later, we added the app_subscriptions object that enables you to query all of your app's subscriptions.
This call only works for app collaborators.
query {
app_subscriptions (app_id: 1234567890) {
cursor
total_count
subscriptions {
account_id
monthly_price
currency
}
}
}