Using the new objects endpoint, you can now query monday.com objects. Objects are a core component of the platform API that represent a generic item within the monday.com platform.
This query returns a JSON object containing metadata about a collection of objects.
query {
objects(
limit: 4,
state: ACTIVE,
order_by: CREATED_AT
) {
id
name
owners {
id
name
}
}
}
You can also create, update, and delete objects via the API using the following mutations:
Using the existing create_column mutation, you can now create connect board and mirror columns via the API. You can query the new get_column_type_schema object to retrieve the available properties for each column type.
mutation {
create_column(
board_id: 1234567890
title: "Related items (Board 9876543210)"
column_type: board_relation
defaults: {
boardIds: [9876543210]
allowMultipleItems: true
allowCreateReflectionColumn: true
}
) {
id
title
type
}
}
You can now retrieve a column’s type-specific schema using the get_column_type_schema object. The response is a JSON object that defines the schema used for creating and updating columns.
You can now use the import_doc_from_html mutation to convert HTML content to a new monday doc. The content is then parsed and converted to the corresponding document block type.
mutation {
import_doc_from_html(
html: """
<!DOCTYPE html>
<html>
<head>
<title>Test Doc</title>
</head>
<body>
<h1>Hello World</h1>
<p>This is a <strong>fake HTML</strong> doc for testing.</p>
<ul>
<li>One</li>
<li>Two</li>
<li>Three</li>
</ul>
</body>
</html>
""",
workspaceId: 1234567890,
title: "New Doc from HTML",
folderId: 9876543210
) {
error
success
doc_id
}
}
You can now use the add_content_to_doc_from_markdown mutation to add markdown content to an existing monday doc. The content is then parsed and converted to the corresponding document block type.
We've updated the format for max complexity per request errors. If you make a request that is more then the allowed complexity, you'll now receive the following error:
We’ve improved how query complexity is calculated and charged:
Complexity is now estimated based on the variables you provide. We charge what we think the query will cost, and once the results are returned, you are reimbursed or charged according to the actual cost. If needed, adjustments are made from the following minute’s allowance.
Failed queries/errors now cost significantly less.
The complexity error format has been updated (read more here).
For many queries, this means that you'll get points back rather than being charged more. These changes make complexity easier to predict and better aligned with API best practices.
