objectives:read scope and require that permission at the deployment root. Writes use the objectives:manage scope together with objectives:read, because every write answers the objective or key result it wrote, and require both permissions at the deployment root, the same permission and home the Console’s objective writes use. A tenant-only grant receives 403 permission_denied. The built-in apps never receive objectives:manage.
Objective responses include status, parent, dates and owner kind. For every worker owner, ownerRefId is null because the stored identifier cannot distinguish a person from an agent. A machine writes only company or orgUnit owners.
Operations
- List objectives — filters and cursor paging, up to 100 rows per page
- Get objective — one objective by id
- List key results — an objective’s key results, up to 200 per page, continued with
meta.nextCursor
Write operations
- Create objective — a
DRAFTobjective owned by the company or an org unit - Update objective — title, description, owner, status or target date
- Archive objective — status
CANCELLED; nothing is deleted - Add key result — starts at
currentValue: 0andON_TRACK - Update key result — title, target, progress, unit or status
- Remove key result — a permanent delete
Idempotency-Key. A same-key retry within 24 hours returns the recorded result only while the caller still holds objectives:read and objectives: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 objective 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.
