ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When integrating with the Sketch REST API, authentication is managed via an API token passed in the Authorization header. While requests missing a token consistently return a 401 Unauthorized response, there is uncertainty regarding the API's behavior when a token is syntactically valid but lacks the necessary permissions for a specific resource. The goal is
Trello REST API When retrieving a large volume of cards from a single board, the API requires the use of the limit parameter to bound result sets and prevent payload timeouts. To retrieve the full dataset, a client must execute multiple sequential requests. There is a conflict between the need for high-frequency pagination to clear a large queue and the API'
When retrieving large datasets from the Azure DevOps REST API, the $top and $skip parameters are used to manage the payload size. However, there are documented constraints regarding the maximum allowed values for these parameters to prevent server-side performance degradation. A specific challenge arises when implementing a paginated sequence to fetch thousa
Goal: Retrieve complete datasets from pfSense REST API endpoints (e.g., firewall rules) using the limit and offset parameters without losing records due to unexpected empty responses. Uncertainty: In pfSense versions 2.6.0‑2.7.2, combining a very large offset (e.g., >100,000) with a small limit can cause the API to return an empty array instead of adjusti
When retrieving large job or build collections via the Jenkins REST API, the goal is to bound the query and paginate results to avoid excessive payloads and controller load. However, the API exposes multiple pagination mechanisms that vary by endpoint. The classic /api/json endpoint supports a tree parameter for field filtering and depth control, while job-s
When integrating external automation with the Bitbucket Server/Data Center REST API, network timeouts during POST requests create uncertainty regarding whether a resource was successfully created on the server before the connection dropped. Because standard write endpoints for entities like pull requests or repositories do not natively support idempotency ke
Goal To determine whether Confluence’s Space Management allows a space key to be altered after the space has been created, and to understand the circumstances under which the REST API returns the “Cannot find space” error. Constraints The documented REST endpoint /rest/api/space/{spaceKey} returns a 404 with the message “Cannot find space” when the key does
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 limi
Defining Write-Safety for Non-Idempotent Methods The OpenAPI Specification (OAS) provides a framework for describing API interfaces, but it lacks a dedicated keyword to explicitly mark an endpoint as idempotent. While PUT and DELETE are inherently idempotent per RFC 7231, POST requests often require custom logic—such as the use of an Idempotency-Key header—t
trello
jenkins
bitbucket
confluence
jiraalign
openapi