---
title: "Update Desk Autonomy"
method: PUT
path: "/desk/autonomy"
tags: ["Desk"]
---

# Update Desk Autonomy

`PUT /desk/autonomy`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/desk/autonomy`
- Auth: HTTP bearer

Decide what the desk may do WITHOUT asking this rep first.

This is not a preference. A lane of `autopilot` means the desk executes
that decision type on the rep's behalf, and the types that can be automated
include ones that reach a real person - which is why `POST /desk/decisions/
{id}/undo` exists at all, and why this operation is not tiered a plain
`write`.

`lanes` MERGES into the stored map rather than replacing it, and a lane
asking for autopilot on a type with no executor is downgraded rather than
refused - so a bulk save echoing back a stale lane still succeeds. An
omitted `autonomy_families` leaves the family answers alone; an explicit
`{}` clears them.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- DeskAutonomyUpdate: Which decisions the desk may act on WITHOUT asking the rep first. A lane of `autopilot` means the desk executes that decision type on the rep's behalf - including the ones that send. `approve` asks first, `off` stops the type being raised at all. The app validates both maps against its own `DecisionType` / `AutonomyLane` / lane-family vocabularies and answers 400 on anything it could not act on, so this surface forwards them as open maps rather than freezing a copy of three enums that move with the product. An omitted `autonomy_families` means "I did not touch the family questions", so a partial save cannot wipe them. An explicit `{}` clears them and hands every type back to its own lane - the only way back once a family has been answered.
  - `lanes` object, required: Map of decision_type -> lane (autopilot/approve/off).
  - `autonomy_families` object, nullable: Map of lane family -> lane (plan_work/outreach/hygiene_and_alerts). Omit to leave family answers untouched; send `{}` to clear them.

## Response `200`

Successful Response

- ApiResponseDeskPayload
  - `data` DeskPayload, required: An open envelope for one desk object. Open on purpose - see the module docstring. A rebuilder gets every field the desk returns, including ones added after this contract version.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/89fc11143b70?raw)