Jira Align API maxResults Limit 400 Bad Request

400 Bad Request when maxResults exceeds limit in Jira Align API

26.5K reputation · 07 Mar 2021, 22:51 UTC

85.2K views0

The Jira Align REST API utilizes startAt and maxResults parameters to manage large dataset retrievals. While the default for maxResults is typically 50, there is a documented hard upper bound of 100 per request.

When a request is initiated with a maxResults value greater than 100, the server returns a 400 Bad Request. However, it is unclear whether this limit is globally fixed across all endpoints or if it varies based on the specific resource type (e.g., Epics, Features, or User Stories).

Is there a mechanism to dynamically increase this 100-item limit for tenant-specific configurations? Does the API provide a Link header in the response to facilitate sequential page-based navigation when the hard limit is reached?

Keep exploring this topic

Focus Trap vs Native Restoration in Jira Align Modals

Jira Align’s modal dialogs lack a consistent focus‑trap, risking keyboard navigation loss. Should all modals adopt a focus trap or continue with native focus restoration, considering dynamic content and performance?

Preventing duplicate writes during Invoke-RestMethod retry loops

Exploring strategies to prevent duplicate data writes when implementing custom retry loops for Invoke-RestMethod in PowerShell.

Configuring pfSense REST API Pagination for Large Offset Queries

Investigating the pfSense REST API’s limit/offset pagination behavior when large offsets produce empty pages, and seeking guidance on safe offset ranges or alternative pagination approaches.

400 Bad Request during deep paging of Work Item Tracking collections

Addressing the 400 Bad Request error and data consistency challenges when using $top and $skip for large Azure DevOps Work Item Tracking datasets.

400 Bad Request when maxResults exceeds limit in Jira Align API

0 answers

Your perspective belongs here.

0 question comments