Skip to main content
  • 300 Product updates

What's new in API version `2023-10`

We released API version 2023-10 on July 1! It features many new and exciting updates, as well as a handful of breaking changes (read more about API versioning here). We put together this guide (complete with a detailed explanation for each change) to help make the transition to the new version easier! Check out all of the changes below, and make sure to click on each item’s respective link to see the full details about each update 😃 After checking out the updates, we would love to hear from you! Your opinions and feedback are vital to building, maintaining, and improving our API. Feel free to submit our feedback form or post any questions in the comments below! Here’s what’s new 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 a required field Empty parentheses are no longer supported Quotation marks for strings are now required Removed the deprecated pos fields on boards and columns queries 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 Non-breaking changes New move_item_to_board mutation New linked_items field on items queries New edit_update and delete_update webhooks The value argument in the change_simple_column_value mutation is now nullable The complexity of the text field for mirror, link, and dependency columns increased

Update to sandboxing for all iframes part 2

Part 2 of sandboxing for all iframes will now be implemented on July 5th, 2023 to give developers more time to test their apps against the new restrictions. Please note that the original directives will remain the same: allow-forms: Allows the page to submit forms. The form will be displayed as normal, but submitting it will not trigger input validation, sending data to a web server, or closing a dialog if this keyword is not used. allow-downloads: Allows downloading files through an <a> or <area> element with the download attribute and through the navigation that leads to a file download. This works regardless of whether the user clicked on the link or JS code initiated it without user interaction. allow-presentation: Allows embedders to have control over whether an iframe can start a presentation session . allow-same-origin: The resource is treated as being from a special origin that always fails the same-origin policy (potentially preventing access to data storage/cookies and some JavaScript APIs) if this token is not used. allow-scripts: Allows the page to run scripts (but not create pop-up windows). This operation is not allowed if this keyword is not used. If you need to open a link in a new tab, you can use the new monday.execute("openLinkInTab") method. We recommend testing your app in the sandboxed environment with the new restrictions to ensure nothing breaks. You can do so by adding the _apps_sandbox=v2 query param to a monday URL. If something breaks and there’s no workaround, please complete a support request so we can find a resolution.

Reminder: Sandboxing for all iframes part 2

NB: This change has been postponed. Learn more here. We previously announced part 1 of sandboxing for all iframes and are getting closer to implementing part 2 on June 28th, 2023! This involves limiting relevant apps’ actions and only allowing the following directives in our iframes: allow-forms: Allows the page to submit forms. The form will be displayed as normal, but submitting it will not trigger input validation, sending data to a web server, or closing a dialog if this keyword is not used. allow-downloads: Allows downloading files through an <a> or <area> element with the download attribute and through the navigation that leads to a file download. This works regardless of whether the user clicked on the link or JS code initiated it without user interaction. allow-presentation: Allows embedders to have control over whether an iframe can start a presentation session. allow-same-origin: The resource is treated as being from a special origin that always fails the same-origin policy (potentially preventing access to data storage/cookies and some JavaScript APIs) if this token is not used. allow-scripts: Allows the page to run scripts (but not create pop-up windows). This operation is not allowed if this keyword is not used. We recommend testing your app in the sandboxed environment with the new restrictions to ensure nothing breaks. You can do so by adding the _apps_sandbox=v2 query param to a monday URL. If something breaks and there’s no workaround, please complete a support request so we can find a resolution.