Starting today, we have a new support form to open a technical ticket with our team! This new form helps us to route your requests and gather useful information about the issues you are experiencing. This will allow us to address your concerns more effectively and provide you with a faster resolution.

The [email protected] email address will no longer be valid. It is set to auto-close and will become a no-reply email address. Moving forward, we encourage all developers to utilize our new support form. App users should reach out via the monday.com support center as usual.

This transition is aimed at improving the support process and enhancing your overall developer experience with our API and app marketplace!

On Jan 16th 2024, we will begin a gradual release of API version 2024-01 as the stable and default version.

If you've migrated your apps already (to 2023-10 or beyond) and want to use an up-to-date API version, you can:

• Pass the version header in every request: "API-Version" : "2024-01"
• Use the setApiVersion option if using the Javascript SDK

Take note of this slight update from the previous announcement – we originally communicated the change would be in effect at 00:00 GMT.

You can now query a workspace's team owners using the team_owners_subscribers field on a workspaces query. This field is available in API versions 2024-01 and later. You can read more about workspaces and the supported fields in our documentation!

Example

The following query would return the name and ID of the team owners in workspace 1234567.

query {
  workspaces (ids: 1234567) {
    team_owners_subscribers {
      name
      id
  }
}

In API versions 2024-01 and later, you can use the new delete_teams_from_board mutation to remove teams from a board. You can find more info about this new query in our documentation!

Example

The following example would remove teams 123456, 654321, and 012345 from board 1234567890.

query {
  delete_teams_from_board (board_id: 1234567890, team_ids: [123456, 654321, 012345]) {
    id
  }
}

In API versions 2024-01 and later, you can add the kind argument to an add_teams_to_board mutation to specify the team's role on the board. If this argument is not used, the team will automatically be added as a subscriber. Check out our documentation for more info!

Example

The following example would add teams 654321 and 123456 to board 1234567890 as owners.

mutation {
  add_teams_to_board (board_id: 1234567890, kind: owner, team_ids: [654321, 123456]) {
    id
  }
}

We recently introduced a hotfix to 2023-10 that returns "" instead of null for most empty column values when querying the text field through column_values V2. This hotfix aligns the 2023-10 behavior to what was returned in 2023-07.

Each column does NOT have the same expected behavior. It is essential to check out the column types reference to verify the expected result for each column.

The list below summarizes the expected behavior:

• Most columns will return "" if the column is empty; otherwise, they'll return the column value as text
• Mirror, connect boards, and dependency columns will always return null
• monday doc columns will always return ""
• Color picker, status, and dropdown columns will return null if the column is empty; otherwise, they'll return the column value as text
• Some other columns (e.g., vote) will return a default value if the column is empty

The new pricing_version field on app_subscription queries returns the subscription's pricing version. This field is only available on API versions 2024-01 and later.

query {
  app_subscription {
    pricing_version
   	billing_period
    renewal_date
  }
}

We just added the direction and symbol fields on the NumbersValue implementation. You can use these fields to return information about the symbols used in Numbers columns. Check out the details here!

Please note that the NumbersValue implementation is only available in API version 2023-10 and later.

Sample query

query {
  items (ids:[9876543210]) {
    column_values {
      ... on NumbersValue {
        number
        id
        symbol
        direction
      }
    }
  }
}

Returns

{
  "data": {
    "items": [
      {
        "column_values": [
          {
            "number": 10,
            "id": "numbers",
            "symbol": "$",
            "direction": "left"
          }
        ]
      }
    ]
  },
  "account_id": 1234567
}

In API version 2023-10 and later, you can add the ids argument to an updates query to retrieve a specific update(s) using its ID.

You can use the argument when querying updates at the root or while nested under boards or items. Please note that when nesting updates in a boards or items query, the ids argument will only return updates matching the ID that are also related to the board or item.

The following example would only return information about update 9876543210 on item 1234567890.

query {
  items (ids: 1234567890) {
    updates (ids: 9876543210) {
      body
      created_at
    }
  }
}

The new app_installs object allows you to retrieve your app's installation data through the API. Your query can return most of the same installation information sent through webhooks.

This new object is available in API versions 2024-01 and later. Check out our documentation for more info!

query {
  app_installs (app_id: 123456789, limit: 1, page: 1) {
    app_id
    timestamp
    app_install_account {
      id
    }
    app_install_user {
      id
    }
    app_version {
      major
      minor
      patch
      type
      text
    }
  }
}