Jira Align REST API and external reporting system: pagination mode for large datasets

Integration goal

Pull large work-item datasets from Jira Align into an external reporting system while keeping response times stable as the result set grows.

Constraint

Offset-based pagination forces the server to scan and discard rows before each offset, so latency rises with page depth. Cursor-based pagination avoids this only if the API exposes a stable monotonic identifier and guarantees sort order across pages. It is not established whether Jira Align's published API offers cursor tokens, supports only offset and limit, or promises deterministic ordering for paginated collections.

Assumption

Targeting the Jira Align REST API. Endpoint names, parameter names, and pagination behavior are treated as unverified until checked against the current API reference for the deployed version.

Questions

Does Jira Align support cursor-based pagination for entity collections, or is offset-based pagination the only supported mode?

If cursor pagination exists, which fields compose the cursor, and is sort order deterministic across pages?

What version assumptions govern pagination behavior in the Jira Align REST API?