Skip to main content
Deprecation notice

Deprecation notice: server-side usage of monday-sdk-js

Related products:Apps Framework
  • December 21, 2025
  • 2 replies
  • 106 views

gregra
Forum|alt.badge.img

Hi developers,

We’re continuing to evolve monday’s developer platform to align with modern JavaScript runtimes and frameworks. As part of this, we’re updating our guidance for how apps should make server-side API calls.

What’s changing

Modern Node versions (Node 18+) include native fetch. Because monday-sdk-js relies on node-fetch for server-side usage, this can cause errors in modern JavaScript frameworks such as Next.js.

Because of this, and based on how the platform has evolved, we are updating our recommended approach for server-side API interactions.

Server-side usage of monday-sdk-js is being deprecated

We are deprecating server-side usage of monday-sdk-js.

In an upcoming major release of monday-sdk-js (v1.0.0), all server-side support will be removed. Client-side usage is not affected at this time.

This is a deprecation notice, not a breaking change. Existing versions of monday-sdk-js will continue to work, but no new server-side features or compatibility fixes will be added. 

What to use instead

For all server-side interactions with the monday platform API, @mondaydotcomorg/api is now the recommended and officialy supported SDK.

This SDK:

  • Uses native fetch
  • Fully supports modern JS frameworks
  • Provides full TypeScript support
  • Offers improved developer experience

Migrating is straightforward

You can continue using your existing GraphQL queries. The new SDK supports passing query strings directly.

Server-side example

import { ApiClient } from "@mondaydotcomorg/api";
const client = new ApiClient({ token });
const result = await client.request<{ boards: { name: string }[] }>(
`query { boards(ids: some_id) { name } }`
);

Client-side usage

Client-side API calls are still supported in two ways:

  • Continue using monday-sdk-js for view apps
  • Or use @mondaydotcomorg/api, including the SeamlessApiClient, which does not require an API token in monday view apps

What you should do now

If your app:

  • Uses modern js frameworks (such as Next.js 14+)
  • Makes API calls from the backen

You should plan to migrate server-side logic to @mondaydotcomorg/api

Thanks for building with monday.

The monday Apps Framework team 💙

 

2 replies

Forum|alt.badge.img
  • Participating Frequently
  • December 22, 2025

Thank you for this ​@gregra!

I have a couple of questions:

  • Do you have an ETA for deprecating monday-sdk-js on the server side? Is there an official date when server-side support will be fully removed, i.e., a target date for version 1.0.0?

  • On the client side, it looks like there are two options: monday-sdk-js and @mondaydotcomorg/api using SeamlessApiClient. What do you recommend? Will they coexist for a while, and is there a timeline for one to replace the other?

Thanks!


gregra
Forum|alt.badge.img
  • Author
  • Leader
  • December 22, 2025

Hey ​@MiguelAngel 

1. As soon as possible, probably this week to publish version 1.0.0 without server side support. It won't affect you, as you will keep on using the existing ask as long as you like, or until you decide to opt in into the 1.0.0 version

2. Indeed there are two options. My recommendation is to move to the SeamlessApiClient as it supports types and better DX (but we are not deprecating it in 1.0.0)