What completing this cycle would do with the work still open in it
GET/api/cycles/{cycle_id}/carryover
cycleCarryover
Names the move BEFORE it happens, so a client can say it in the confirmation rather than guessing: how many unfinished issues the cycle holds, and which cycle they would move to (`to_cycle: null` = they become uncycled, because the team has no later cycle). A forecast, not a reservation — the completion receipt reports what was actually moved.
Requires authentication using a bearer token or a session cookie — see tokens and scopes.
curl
curl -X GET 'https://neosource.dev/api/cycles/CYCLE_ID/carryover' \
-H 'Authorization: Bearer $NEOSOURCE_TOKEN'fetch
fetch("https://neosource.dev/api/cycles/CYCLE_ID/carryover", {
method: "GET",
headers: {
Authorization: "Bearer $NEOSOURCE_TOKEN",
},
});Path parameters
cycle_idrequired
Responses
200Carryover plan
application/json
403Forbidden — one of: forbidden, needs_scope
application/json
one of
Standard errors
Bodies documented once for the whole API — see standard errors.
- 400Bad Request — one of: invalid_input
- 401Authentication required
- 404Not Found — one of: not_found
- 429Rate limited — retry after the `Retry-After` header
- 500Internal server error
- 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
- 504Gateway timeout — the request exceeded the server's handling budget