Development best practices

We want to ensure that you have a seamless developer experience with To do so, we've compiled a list of tips, tricks, and development best practices to make your dev journey easier. Whether you're working with our API or developing an app for the marketplace, this list is for you!

API usage

Use a queuing mechanism for mutations and queries to avoid limitations

A queuing mechanism is essential to maintain a good user experience and keep the API healthy if your app has bulk mutations or queries.

Check out these queuing service providers for more information:

Avoid API call timeouts

All API calls follow a 60-second timeout policy. You can avoid timeouts by returning less data per query.

You can return less data by implementing pagination, using limits in your queries, and only returning required information.

Don't create too many items at the same time

You cannot create more than 10 to 20 items in real time. Each create_item mutation uses 10,000 complexity points, which means you can make ~160 items per minute to avoid hitting the complexity limit.

For example, you'll need to queue your mutations if you need to create 1,000 items.

Do not make API calls concurrently

You should make all mutations one after the other. If you make multiple mutations on the same board simultaneously, the data on the board can become corrupted.

Storage API

Understand the limits of the storage API

The storage API has both instance level and account level storage. When using instance-level storage, different views cannot access the same data.

If you'd like to access data between different views, you'll need to use the global storage methods.

For more information on our Storage API (not to be confused with the monday GraphQL API), please see our SDK Reference here.