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!
You can now update one or multiple users' attributes through the update_multiple_users mutation.
mutation {
update_multiple_users (
user_updates: [
{
user_id: 12345678,
user_attribute_updates: {birthday: "1985-06-01", email: "[email protected]"}
},
{
user_id: 87654321,
user_attribute_updates: {birthday: "1975-01-20", email: "[email protected]"}
}
]
) {
updated_users {
name
birthday
email
id
}
errors {
message
code
user_id
}
}
}
Variables can now only be sent as a JSON object instead of a JSON string. Queries using JSON string variables will fail. This update impacts all users and queries where the variables were previously sent as a string.
Check out the example below of the same query before and after this change:
{
"query": "query GetBoardItems($boardId: [ID!]) { boards(ids: $boardId) { items_page(limit: 1) { cursor items { id subitems { id name column_values { column { title } text ... on MirrorValue { display_value } ... on BoardRelationValue { linked_item_ids linked_items { name } } } } } } } }",
"variables": {
"boardId": 7670657643
}
}
{
"query": "query GetBoardItems($boardId: [ID!]) { boards(ids: $boardId) { items_page(limit: 1) { cursor items { id subitems { id name column_values { column { title } text ... on MirrorValue { display_value } ... on BoardRelationValue { linked_item_ids linked_items { name } } } } } } } }",
"variables": "{\"boardId\":7670657643}"
}
The create_webhook mutation now returns InvalidArgumentException errors when:
Check out the sample error responses below:
{
"data": {
"create_webhook": null
},
"errors": [
{
"message": "Board not found",
"locations": [
{
"line": 1,
"column": 10
}
],
"path": [
"create_webhook"
],
"extensions": {
"code": "InvalidArgumentException",
"status_code": 200,
"error_data": {
"board_id": 1186075578
}
}
}
]
}
{
"data": {
"create_webhook": null
},
"errors": [
{
"message": "Creating webhook on subitems board isn't allowed",
"locations": [
{
"line": 1,
"column": 10
}
],
"path": [
"create_webhook"
],
"extensions": {
"code": "InvalidArgumentException",
"status_code": 200,
"error_data": {
"board_id": 118607557
}
}
}
]
}
The new end_date field on the app subscription details object allows you to query the date an inactive subscription ended. It returns null for any subscriptions with an active status.
query {
app_subscriptions (app_id: 1234567890) {
cursor
total_count
subscriptions {
account_id
monthly_price
currency
status
end_date
}
}
}
The renewal_date field on the app subscription details object is no longer required. It has changed from type String! to String, and the field will return null for inactive subscriptions.
query {
app_subscriptions (app_id: 1234567890) {
cursor
total_count
subscriptions {
account_id
monthly_price
currency
renewal_date
}
}
}