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 item
• created_at: Returns the creation date of the timeline item

query {
  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.

Sample responses

2025-01 and later

{
  "data": {
    "boards": [
      {
        "id": "9876543210"
      }
    ]
  }
}

2024-10 and earlier

{
  "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
      }
    }
  }
}

We have made a handful of improvements to our rate limits to help maintain a high-quality API and support optimal performance. Some of these updates include:

1. Standardized error codes: Rate limit errors will now return a 429 HTTP error code to help standardize responses and simplify error handling.
2. Retry-After header: Errors will now include the Retry-After header to indicate how long you need to wait before making another request.
3. New rate limits: We've introduced new limits, including per-minute request limits and a concurrency limit. These changes help reduce the frequency of complexity limits, giving you more control over your API usage and providing a smoother developer experience.
4. Daily limits: Daily request limits will be enforced for basic and standard accounts starting next week. Limits for pro and enterprise accounts will be gradually rolled out next year.

For more information, check out our rate limits documentation. Questions or comments? Add them here!

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
      }
    }
  }
}