The renewal_date field on the app subscription details object is no longer required. It has changed from type String! to String, and the field will return null for inactive subscriptions.
query {
app_subscriptions (app_id: 1234567890) {
cursor
total_count
subscriptions {
account_id
monthly_price
currency
renewal_date
}
}
}To improve error consistency, we've released a bug fix that impacts the error response format for complexity budget exhausted errors. This fix applies to versions 2025-01 and later.
Now, errors are returned in the following format when the complexity budget is exhausted:
{
"errors": [
{
"message": "Complexity budget exhausted",
"extensions": {
"code": "COMPLEXITY_BUDGET_EXHAUSTED",
"complexity": 6182,
"complexity_budget_left": 100,
"complexity_budget_limit": 5000000,
"retry_in_seconds": 60,
"status_code": 429
}
}
]
}You can now invite users to join a monday.com account using the new invite_users mutation. This is available in API versions 2025-04 and later.
mutation {
invite_users (emails: ["[email protected]", "[email protected]"], product: crm, user_role: VIEW_ONLY) {
errors {
message
code
email
}
invited_users {
name
id
}
}
}In API versions 2025-04 and later, you can create page break blocks using the create_doc_block mutation.
mutation {
create_doc_block (type: page_break, doc_id: 1234567, after_block_id: "a3f6b7c9-ee2f-5b10-8921-cc47e7d745d3", content: "{\"alignment\":\"left\",\"direction\":\"ltr\"}") {
id
}
}Starting in version 2025-01, GraphQL queries must be sent in the request body. They will fail if passed in the query param of the URL.
For example, the following query would fail in versions 2025-01 and later:
https://api.monday.com/v2?query=query { me { id } }
To make the call work, include the GraphQL query in the request body:
query {
me {
id
}
}In API versions 2025-01 and later, the updates query will return a maximum of 100 updates per page. To retrieve all updates, you'll need to paginate through the subsequent pages.
For example, the following query will return the first page of 100 updates. You can modify the page argument to return additional pages.
query {
updates (page: 1) {
id
text_body
}
}In 2025-01, we added the following fields to the timeline_item endpoint:
content: Returns the content of the timeline itemcreated_at: Returns the creation date of the timeline itemquery {
timeline_item (id: 1234567890) {
board {
id
}
item {
name
}
id
user {
id
name
}
title
type
content
created_at
}
}Starting in API version 2025-01, the account_id will no longer be returned in all responses by default. If you need the ID, you can still retrieve it through an account query.
{
"data": {
"boards": [
{
"id": "9876543210"
}
]
}
}{
"data": {
"boards": [
{
"id": "9876543210"
}
]
},
"account_id": 12345678
}In API versions 2025-01 and later, you can activate users through the API using the new activate_users mutation!
mutation {
activate_users (user_ids: [54321, 12345]) {
activated_users {
id
name
email
}
errors {
user_id
code
message
}
}
}In API versions 2025-01 and later, you can query the Emails & Activities timeline of a specific item using the timeline object.
query {
timeline (id: 1234567890, limit: 5, cursor: "TXlDb2RlU3RyaW5nMTIzNDU2NzgsNzg5MCxzb21lRGF0YT1Bbm90aGVyVmFsdWU=") {
timeline_items_page {
cursor
}
timeline_items {
title
custom_activity_id
board {
workspace_id
}
}
}
}