Skip to main content
A roadmap is a named planning container owned by the company, a department or a team. Roadmap reads use the objectives:read scope and require that permission at the deployment root, the same permission and home the Console uses; planning rows carry no home of their own. Writes use the projects:manage scope together with objectives:read, because every write answers the roadmap it wrote, and require both permissions at the deployment root. A tenant-only grant receives 403 permission_denied.

Operations

  • List roadmaps — by owner, by status, or newest first; cursor paging up to 100 rows
  • Get roadmap — one roadmap by id

Write operations

Roadmaps are never deleted over the API. Every write accepts an optional Idempotency-Key. A same-key retry within 24 hours returns the recorded result only while the caller still holds objectives:read and projects:manage at the deployment root; otherwise 409 idempotency_result_unavailable, and the write never runs twice. A successful write records no audit event, as the Console’s planning writes record none; a refused write records a denial. List cursors are bound to the filters that created them. Reusing one with different filters returns 400 bad_request.