Missing total field in Bamboo /api/plan pagination prevents determining total record count

Short answer: no. The Bamboo plan-list resource (typically /rest/api/latest/plan) does not expose a total field, and there is no documented companion endpoint or query parameter that returns just the plan count. This is confirmed behavior for the resource itself; what follows about workarounds is the practical recommendation, and the exact paging fields vary by Bamboo version, so verify against your instance.

Why isLastPage is the only reliable terminator

The paging metadata you see — size, limit/max-result, start-index, isLastPage — is all Bamboo guarantees. Two traps to avoid:

• Do not treat a short or empty page as the end. Permission filtering can produce partial pages mid-stream, so a page smaller than max-result does not mean you're done. Only isLastPage=true is authoritative.
• Do not assume a huge max-result fetches everything in one call. Values above the server cap are silently clamped, so you'd get a capped page with isLastPage=false and no warning.

Recommended approach

Page with a reasonably large max-result (e.g., 100–500), accumulate size from each response, and stop at isLastPage=true. The summed size is the total:

total=0; start=0
while true; do
  r=$(curl -s -u user:token \
    "$BAMBOO/rest/api/latest/plan?max-result=200&start-index=$start")
  n=$(jq '.plans.size' <<<"$r")
  total=$((total+n))
  [ "$(jq '.plans.isLastPage' <<<"$r")" = "true" ] && break
  start=$((start+n))
done
echo $total

If you only need the count and want to save bandwidth (not round trips), request max-result=1 and count pages — but you still traverse to the end, so this rarely wins over summing sizes on pages you'd fetch anyway.

If the count is displayed, not computed once

Plans change far less often than builds. The standard pattern is to compute the count once via traversal, cache it, and invalidate on plan create/delete events (webhooks or a periodic refresh). That gives you progress percentages without per-request full scans.

Verify before hardcoding

Bamboo Server/DC REST behavior differs across versions. Before committing to traversal:

1. Call /rest/api/latest/plan?max-result=1&start-index=0 on your instance and inspect exactly which paging fields come back.
2. Page to isLastPage=true and confirm the summed sizes match the plan count shown in the Bamboo admin UI.
3. Check the REST docs bundled with your Bamboo version for any newer total-count support on this resource.

One caveat worth flagging for review: some Bamboo resources accept expand parameters that surface extra metadata, but a total count for the plan list is not reliably among them — treat that as version-dependent and unconfirmed until you test it on your instance.