We have made a handful of improvements to our rate limits to help maintain a high-quality API and support optimal performance. Some of these updates include:
Standardized error codes: Rate limit errors will now return a 429 HTTP error code to help standardize responses and simplify error handling.
Retry-After header: Errors will now include the Retry-After header to indicate how long you need to wait before making another request.
New rate limits: We've introduced new limits, including per-minute request limits and a concurrency limit. These changes help reduce the frequency of complexity limits, giving you more control over your API usage and providing a smoother developer experience.
Daily limits: Daily request limits will be enforced for basic and standard accounts starting next week. Limits for pro and enterprise accounts will be gradually rolled out next year.
For more information, check out our rate limits documentation. Questions or comments? Add them here!
In API version 2025-01 and later, column validations for apps will be enforced for all columns. Invalid JSON will return a ColumnValueException error code.
In API versions 2025-01 and later, you can read the formula column using the display_value field. This field returns the content of the formula column as a string.
This feature is in an early release phase and has the following limitations:
Formulas that use mirror columns are not supported.
You can retrieve up to 10,000 formula values per minute.
You can query up to five formula columns in one request.
As we do additional testing and development, these limitations will gradually be reduced or removed.
query {
boards(ids: [1234567890]){
items_page(limit:2){
items{
id
column_values {
...on FormulaValue{
display_value
id
type
}
}
}
}
}
}