You can now update a user's custom role using the role_id argument on the update_users_role mutation. You can obtain available role_id values by querying the new account_roles type.
Custom roles are only available on Enterprise plans.
mutation {
update_users_role (user_ids: [12345, 54321], role_id: "5") {
updated_users {
name
}
errors {
user_id
code
message
}
}
}
You can now query an account's roles through the new account_roles object. This query returns metadata about an account's user roles (both default and custom).
query {
account_roles {
id
name
roleType
}
}
{
"data": {
"account_roles": [
{
"id": "1",
"name": "admin",
"roleType": "basic_role"
},
{
"id": "2",
"name": "member",
"roleType": "basic_role"
},
{
"id": "3",
"name": "view_only",
"roleType": "basic_role"
},
{
"id": "4",
"name": "guest",
"roleType": "basic_role"
}
]
}
}
We increased the maximum dimensions of workdoc tables. You can now create tables up to 25 rows tall and 10 columns wide.
Example query:
mutation {
create_doc_block (
type: table,
doc_id: 500152767,
content: "{\"column_count\": 10, \"row_count\": 25}"
) {
id
}
}
We delivered this feature because we got multiple requests for it from our developer community. If you have a feature request, submit it to us through the developer's category.
The value field for connect boards, dependency, and subtask columns will now return null instead of including linked item IDs and their last updated timestamp. This change improves overall column values performance.
You can retrieve this information by querying the relevant fields directly (read more below).
The following examples show the same query's behavior before and after this change.
query {
boards(ids: 1234567890) {
items_page {
items {
column_values (types: board_relation) {
value
id
}
}
}
}
}
{
"data": {
"boards": [
{
"items_page": {
"items": [
{
"column_values": [
{
"value": "{\"changed_at\":\"2025-03-18T18:27:14.832Z\",\"linkedPulseIds\":[{\"linkedPulseId\":9876543210}]}",
"id": "connect_boards"
}
]
}
]
}
}
]
}
}
query {
boards(ids: 1234567890) {
items_page {
items {
column_values (types: board_relation) {
value
id
}
}
}
}
}
{
"data": {
"boards": [
{
"items_page": {
"items": [
{
"column_values": [
{
"value": null,
"id": "connect_boards"
}
]
}
]
}
}
]
}
}
To retrieve the missing data, query the linked_items and linked_item_ids fields directly as shown below.
query {
boards(ids: 1234567890) {
items_page {
items {
column_values (types: board_relation) {
value
... on BoardRelationValue {
linked_item_ids
linked_items {
name
updated_at
}
}
id
}
}
}
}
}
{
"data": {
"boards": [
{
"items_page": {
"items": [
{
"column_values": [
{
"value": null,
"linked_item_ids": [
"9876543210"
],
"linked_items": [
{
"name": "Item 4",
"updated_at": "2023-08-29T15:38:11Z"
}
],
"id": "connect_boards"
}
]
}
]
}
}
]
}
}
We've recently added two new fields to the users object, making it easier to query and manage custom fields in the user profile:
custom_field_metas: Retrieves metadata about the custom field, including its type, description, and whether or not it is editablecustom_field_values: Fetches the values users input into the custom fieldThe example below retrieves the custom fields' type, description, id, and editability using the custom_field_metas field. It also retrieves the fields' meta ID and value using the custom_field_values field.
query {
users (ids: 1234567) {
custom_field_metas {
field_type
description
id
editable
}
custom_field_values {
custom_field_meta_id
value
}
}
}
You can now use the max_units argument in set_mock_app_subscription mutations to define the maximum number of seats allowed on a mock plan for seat-based apps.
mutation {
set_mock_app_subscription (
app_id: 12345,
partial_signing_secret: "abcde12345",
is_trial: true,
plan_id: "basic_plan_15_users",
max_units: 15
) {
plan_id
}
}
You can now query the max_units field on app_subscription queries.
null.query {
app_subscription {
billing_period
days_left
is_trial
plan_id
renewal_date
max_units
}
}
If you reach the IP limit, you will receive the following updated error message. Wait for the duration specified in the retry_in_seconds fields before retrying your request.
{
"errors": [
{
"message": "IP rate limit exceeded",
"extensions": {
"code": "IP_RATE_LIMIT_EXCEEDED",
"retry_in_seconds": 30
}
}
]
}
To help increase performance and provide consistent results for the subitems query, we have changed the way we return results and fetch subitems via the existing query. The following fixes have been introduced:
subitems field. If this limit is exceeded, the following errors will be returned, depending on the API version you're using:{
"data": {
"items": [
{
"subitems": null
}
]
},
"errors": [
{
"message": "Concurrency limit exceeded for the field",
"locations": [
{
"line": 1,
"column": 25
}
],
"path": [
"items",
0,
"subitems"
],
"extensions": {
"code": "FIELD_LIMIT_EXCEEDED",
"status_code": 429,
"retry_in_seconds": 15,
"error_data": {
"entity": "subitems"
}
}
}
]
}
{
"errors": [
{
"message": "Concurrency limit exceeded for the field",
"locations": [
{
"line": 1,
"column": 25
}
],
"path": [
"items",
0,
"subitems"
],
"extensions": {
"code": "FIELD_LIMIT_EXCEEDED",
"status_code": 429,
"retry_in_seconds": 15,
"error_data": {
"entity": "subitems"
}
}
}
],
"status_code": 429,
"error_data": {
"entity": "subitems"
},
"error_code": "FIELD_LIMIT_EXCEEDED",
"error_message": "Concurrency limit exceeded for the field",
"account_id": 12345
}
Through the new API analytics dashboard, you can monitor your account's daily API usage and trends. It provides insights into your overall API consumption, allowing you to track:
The dashboard is currently only available for Enterprise accounts. It is accessible from two locations:
For tips on optimizing your API usage, check out our guide!
