Product updates

I’m here to deliver some good news regarding seamless authentication via the SDK… The shortLivedToken is now valid for 5 minutes instead of 1 🥳 This change will give your app an additional four minutes to make authenticated calls to the API as part of your integration recipe. You can read more about seamless authentication for integrations in our documentation. Happy authenticating!

Hello wonderful community! Dipro here, dropping in with a quick note about the new API version that we’ve been discussing here for the last few months 🔮 Version 2023-10 is now stable, meaning you can confidently use it in production (as of Oct 1, 2023). If you missed our previous announcements about this, here’s some context: Why should I care? This upgrade uses mondayDB, our new proprietary data infrastructure. It also contains quality-of-life improvements like sorting, filtering, and a more consistent way to access column data. Note that there are breaking changes in this release - any apps using deprecated queries should update their usage by January 15th 2024 otherwise they might break. What does this mean for me? Application developers: Rebuild the relevant logic in your apps to use the new API correctly. Anyone using Make, Zapier, or other 3rd party integration tools: These integration providers are updating their connectors. In the coming weeks, they will send you communication on what changes you’ll need to make in your workflow. How can I learn more? Read a list of all the changes – Release notes Read this migration guide – Migrating to version 2023-10 Watch this recent training – API Migration Bootcamp

We released API version 2024-01 on October 1st. It contains just one breaking change to give you more time to focus on the changes previously announced in 2023-10. Check it out below! Here’s what’s new Breaking changes Typo fix in UserUnauthorizedException error

Hi Community In light of the success of his last post and all the great feedback he received from you on Webhooks , Greg, who is leading the apps framework here on monday.com is inviting you to a private call with him. 💻 Why? Greg is looking to get more insights from you regarding the apps framework, and to consult with you on new features that are coming soon. 👂🏽 🎧 How? Here is a link to schedule a session with him. 🔗 Another excellent opportunity for us to learn and for you to influence

We recently added the ability to sort and filter items_page results by either their last updated or creation dates. You can do so by entering either "__creation_log__" or "__last_updated__" as the column ID in the order_by field of your query. The items will be returned chronologically, with the oldest listed first. Please note that you are not required to have a last updated or creation log column on your board to use this sorting mechanism. The following example would return the first 50 items on board 1234567890 with a blank status column value, and they would be listed chronologically (oldest to newest) according to their creation date. query { boards (ids: 1234567890){ items_page (limit: 50, query_params: {order_by: [{column_id: "__creation_log__"}], rules: [{column_id: "status", compare_value: [5]}], operator: and}) { cursor items { id name } } } }

We’ve recently made a few updates and improvements to our webhooks to help provide you with a better developer experience. Let’s check them out! 👀 New app_webhooks_only argument This new argument returns just the webhooks created by the app initiating the request when querying the webhooks object through the API. query { webhooks (app_webhooks_only:true, board_id:1234567890) { id event config } } Missing authorization headers Before these updates, we were missing a feature that sent the authorization header for some webhooks. We added the missing feature, so now the authorization header will be included in all webhooks. Make sure to start validating your requests from monday! Please note that this only applies to apps created in the Developer Center. You will not receive the authorization header if your app uses a personal token. Users can’t remove app webhooks in the UI While webhooks created by apps were always labeled internally on monday as belonging to a specific app, we enabled this labeling in the Active integrations page on the board so users can’t remove your webhooks from the board!

In the 2023-10 API release, we introduced the items_page object which utilizes cursor-based pagination to retrieve smaller groups of items from a large data set. This object must be nested inside of a boards query, so it has a high complexity cost. To help reduce that cost, we created the next_items_page object which can be used at the root of your query to paginate through the data set. It takes both the cursor and limit arguments and retrieves the following page of items in the data set. Now let’s break it down a bit… Say you only want to retrieve items with a blank status column from board 1234567890. This board contains thousands of items that cannot be retrieved simultaneously, so you can use cursor-based pagination. The query below would return the ID and name of the first 50 items with a blank status column and a cursor value that represents the position in the data set after returning 50 items. query { boards (ids:1234567890) { items_page (limit: 50, query_params: {rules: {column_id: "status", compare_value: [5], operator:any_of}}) { cursor items { id name } } } } You can then use the next_items_page object with the cursor argument from the first query to return the following 50 relevant items in the data set. After returning the next cursor value, you can continue paginating through the entire data set. query { next_items_page (limit: 50, cursor: "MSw5NzI4MDA5MDAsaV9YcmxJb0p1VEdYc1VWeGlxeF9kLDg4MiwzNXw0MTQ1NzU1MTE5") { cursor items { id name } } }

We have removed support for the text field on MirrorValue, DependencyValue, and BoardRelationValue column values. We have replaced it with the new display_value field to return text values for the connect boards, dependency, and mirror columns. As part of the 2023-10 release, we created the text field on column_values to return the text values for each column. These calls have a high cost for the mirror, dependency, and connect board columns. Therefore, we stopped supporting the text field and created the display_value field on these three column values only. These updates will help reduce the load by only returning the data when users actually need it. The following example would return the mirror column display values (i.e., text values) on items 1234567890 and 9876543210. query { items (ids:[1234567890, 9876543210]) { column_values { ... on MirrorValue { display_value } } } }

Hi community! It just occurred to us that we are experiencing problems uninstalling apps. The tech team is working on that and it should be fixed in the next few hours.

Hey community! We wanted to let you know that two weeks ago, we made a minor change to the “unsubscribe” behavior of the custom triggers for the Integration/Workflow app feature. Previously, the trigger’s unsubscribe endpoint was only called when the integration or board was deleted. However, we’ve now updated it to also unsubscribe for 3 days (subject to change in the future) after the automation was disabled. The reason for this change is to streamline resources and unsubscribe stale automations that have been out of use for more than 3 days. Prior to this change, such automations could remain disabled but also subscribed to indefinitely, wasting resources on both ends. This change will help both the apps infrastructure and app developers infrastructure save resources, and only trigger truly active automations moving forward. We hope this change makes your app experience even better. 💪🏼 If you have questions or concerns, please contact us. 🌸

We recently updated the DependencyValue implementation, so you can now return both the linked_items and the linked_item_ids for dependency columns when querying through column_values V2. Please note that the DependencyValue implementation is only available in version 2023-10. query { items (ids:[1234567890, 9876543210]) { column_values { ... on DependencyValue { linked_item_ids linked_items } } } }

Hello everyone who joined the webinar today! First off, apologies for the abrupt end to the meeting… We had some technical issues and were dropped from Zoom. Here are some resources that I discussed on the call: Webinar recording Query samples that we covered Release notes with all changes Migration guide Guide to column names and what’s changing PS @PolishedGeek – I was in the middle of your question when we dropped off. Make will be migrating their connector to the new API. I’ve reached out to them already – they are aware of these changes and making the required updates. I don’t know the exact status of it though; if you need a timeline please reach out to them for the most updated information. I will write up the other questions here and post them later today (along with the recording).

The new after_column_id argument on the create_column mutation allows you to specify which column to create the new one after. This argument is available in API versions 2023-07 and later. Check out our documentation for more info! In the following code sample, the new status column would be created after the country column. mutation{ create_column(board_id: 1234567890, title:"Work Status", description: "This is my work status column", column_type:status, after_column_id: "country") { id title description } }

We just added a new breaking change to API version 2023-10: The deprecated items field on the groups object will be removed and replaced with items_page in API version 2023-10 . Please see our previous announcement for more information about the items_page field.

Hi monday devs 😎 In our last event we got multiple questions about the new API version. So we decided to conduct a dedicated office hour about this on Aug 31st. The content will be practical tips about the migration. The things we will cover: New features in version 2023-10 Explanation of the breaking changes How to switch between versions How to migrate your apps — for product developers and account admins Examples of what to update and how Common roadblocks and their solutions The most exciting part is that all of that will be explained and demonstrated by @dipro who is known for his explanation skills (he once won the local grandma test - he explained to his grandma over dinner how to use the monday API 👩🏼‍💻) Want to be part? Register here. Aug 31, 10am EST 💡

We decided to move the deprecation of API version 2023-07 to January 15th, at 8am GMT. This is to account for new year holidays being observed in a many parts of the world. Changelog The date change applies to all the updates that were originally scheduled for Jan 1st:: Version 2024-01 will be released for preview Version 2023-07 will be deprecated You will no longer get 2023-07 as the default version when sending a request without a header We got feedback from our community (YOU) that the date was a bit risky, so we adjusted our plans accordingly 🙂 And even though this gives you a few more days to prepare, we still recommend starting the migration as soon as possible 😉

We’ve added warning messages to a lot of our API calls! For example, if you try and use a deprecated API call, you’ll get an extensions object with a list of warnings in it - link to changelog If you store application logs, I recommend logging these values – it will give you clarity on what functions need to be updated during your migration process! Code example Let’s say I use the items_by_column_values query, which will be deprecated in 2023-10: query { items_by_column_values(board_id:12345, column_id:numbers, column_value:"5000") { id name } } In the returned data, I will receive an extensions object, with a warning that this is being deprecated. It also contains metadata such as what part of my query is deprecated, and a code to explain the cause of the warning. Here’s what it looks like: { "data": { "items_by_column_values": [ { "id": "4579863854", "name": "Develop messaging" } ] }, "extensions": { "warnings": [ { "message": "Replaced by Query.items_page_by_column_values since 2023-10", "locations": [ { "line": 2, "column": 3 } ], "path": [ "query", "items_by_column_values" ], "extensions": { "code": "deprecatedField", "typeName": "Query", "fieldName": "items_by_column_values" } } ] }, "account_id": 12345 } Would love to hear your feedback in the comments below!

Hi community! Thank you for joining our MeetApp webinar. We were very excited to see you all in one virtual space. Here is all the webinar information for you API Migration: All API resources are ready for you in one post here New AI and Board Features: Here you can find the AI assistance documentation and the newly added board feature documentation. App Analytics: Here is app analytics documentation. Follow-up webinar: On Aug 31 we’ll have a deep dive into the 2023-10 API version. Register here. monday - code: register here to the beta program. Give us feedback: help us to create better MeetApps for you by filling out a feedback from. MeetApp recording: here is the link. Passcode: BfDX9+9P You are welcome to ask and consult with us here, as well as to answer other questions via this forum.

I know there are a lot of updates about the new version of the API; I thought I’d compile a list of migration resources here and add to them as I go along. Want email updates for this topic? Click the bell icon at the bottom of this thread and select “Watching” to get an email for every new update! General resources API release notes – list of all the changes with a link to a detailed changelog about each one 2023-10 migration guide – covers the main changes in this version and how to adapt to them. NB: This is not an exhaustive list of changes; I’m adding to it each week! API Versioning Principles – explains our approach to API versioning and when each change will take place Tips about specific topics How to filter items using items_page with examples (from migration guide) Which IDs will stop being integers? How to return mirrored and linked data - using the linked_items field Use API warnings to know when you’re using an outdated API call Livestreams Migration Bootcamp Training Recording Interesting threads & common questions How to switch the API version you are using - in playground and HTTP requests How to handle the alphanumeric ID field I know there’s a lot of different topics to think about when migrating, hope this list is helpful for you! Shoot me a message in the comments if there are specific things you’d like to see resources for.

When a user churns from monday.com, their app subscriptions are also canceled. Therefore, the app_subscription_cancelled webhook will now contain a reason field indicating their subscription was canceled upon renewal. Currently, this is the only instance when the reason field appears, though we plan on adding support for additional reasons in the future. { "type":"app_subscription_cancelled", "data":{ "app_id":1000000000, "user_id":1, "user_email":"user1@users.com", "user_name": "User 1", "user_cluster": 'other', "account_tier": 'free', "account_name": "Demo Account", "account_slug": "test", "account_max_users": 10000, "account_id":777777, "version_data":{ "major":1, "minor":2, "patch":0, "type":"minor" }, "timestamp":"2022-06-23T00:00:00.000+00:00", "subscription":{ "plan_id":"plan1", "renewal_date":"2022-07-19T00:00:00+00:00", "is_trial":false, "billing_period":"monthly", "days_left":26, "pricing_version":5 }, "reason":"monday_subscription_cancel_on_renewal" } }

Using the create_doc mutation, you can now create a new document in a workspace (not just a monday doc column!) This mutation is available in API versions 2023-07 and later. Check it out 🤠 mutation { create_doc (location: {workspace: { workspace_id: 1234567, name:"New doc", kind: private}}) { id } }

An improved app listing page will be soon gradually released and will highlight apps values and content! We’ve been conducting interviews with costumers, testing, designing, and consulting to create a new user experience for users in the marketplace. In that spirit we designed a new listing page for apps. We wanted to make sure the page answered users’ most pertinent questions while considering installing an app What is the app value? What does the app do? Can I trust it? We designed the page to address all these questions, without compromising a top-notch user experience! Therefore, we organized all the information into three sections: Marketing - a top banner that provides a GIST of the app’s value and the most important information to users, to encourage them to keep on reading - with a bigger gallery since it’s the first thing users go to - want to see what it looks like? Check out this loom. Functionality - we gather all the information that will help users understand what the app actually do - capabilities, monday product areas they can find the app in, permissions, pricing, etc Informative - all the ‘dry info’ users might need in order to install and use the app - guides, demos, support, developer website, etcAcross all of it, we added scrolling down behavior (like on landing pages) to create a rich user experience .We tried to design an organized experience that answers all questions while being enjoyable and aesthetic. … #This is just the first phase, there will be more to come and we will keep you posted, so stay tuned. So when? It will be released gradually so we can test users’ reactions to the changes. Having personally witnessed those changes, I believe we are aiming for new wins, and that makes me excited!

Following up from the previous board menu app features announcement… The board item menu is now available, so you can start creating all three new app features 🤠

We previously announced our AI assistant, but the moment you’ve all been waiting for is finally here… Developers can now build AI apps using our AI assistant app features 🙌 We’ve developed six app features that live in various locations in the platform, use different SDK methods, and work best with certain types of apps. You should decide which feature you’d like to build based on your app’s logic: Board header AI assistant Update AI assistant Doc header AI assistant Doc command AI assistant Doc toolbar AI assistant Doc quickstart AI assistant We’ve also compiled a quickstart guide that walks you through each step of creating an AI assistant app feature, but as always, feel free to drop your questions below ⬇️

Hi Community We have an issue with the short lived session token that is not passing properly to the iframe of the app. A fix is on its way to production. We apologize for the situation and are working on fixing the problem as soon as possible. 🙏🏼 I will update here as soon as I have more information regarding the status. 👩🏼‍💻