> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quiva.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set the default space for promoted tasks

> **Account admins only** — this moves where *every* member's promotions and every task Abbie creates herself end up.

`space_id` is required (an omitted field is a 400, never a silent reset; send `ESCALATE` explicitly to return to the built-in default), is uppercased, and is **validated against the account's real spaces before it is stored** — an unvalidated id would sit in the aggregate looking fine and fail on every future promotion. `ESCALATE` is accepted without a lookup because workspaces-service hardcodes it rather than storing it.

An unknown space is 400; a failed space lookup is 502. Subject: `microstrate.hub.put.coworker-task-space`.



## OpenAPI

````yaml /api-reference/endpoint/abbie/openapi.json put /hub/coworker/task-space
openapi: 3.1.0
info:
  title: Abbie API (beta)
  version: 1.0.0
  description: >
    **Beta.** This API is in beta: operations and fields may change without a
    deprecation period. Do not depend on undocumented fields. It covers the
    subset of Abbie's API used by the Quiva coworker MCP server: skills, todos,
    memory, profile, corrections, environment and models.


    HTTP surface of hub-service for Abbie/Coworker configuration, agent rapport
    & context, chat-session sharing, and MCP registration.


    ## Transport and response envelope


    Every operation here is a gateway mapping onto a Bellerophon/kraken subject
    of the form `microstrate.hub.<method>.<endpoint-slug>` (see
    `hub-service/service/service.go` and `docs/abbie-gateway-mappings.md`).
    Handlers reply on the mesh with an envelope `{"status_code": <int>, "body":
    <object>}`; the gateway unwraps it, so `status_code` becomes the HTTP status
    and `body` becomes the HTTP response body. **The schemas below describe the
    unwrapped `body`.**


    Errors are always `{"error": "<message>"}` with the matching HTTP status.


    ## Parameter conventions


    The gateway forwards URL parameters to the handler as request headers:


    - `x-param-query-<name>` — a query-string parameter (`?name=value`)

    - `x-param-<name>` — a path parameter


    Every parameter documented as `in: query` or `in: path` below corresponds to
    one of those headers, and the header suffix is named in each parameter's
    description where it is not obvious.


    ## Authentication


    All operations require the caller's bearer token; the account id, user id
    and user public key are always taken from the JWT and never from the URL or
    body. Endpoints that additionally require an account **admin** role are
    marked in their description — a failed role lookup answers **502**, never
    403 and never a pass.


    ## Two path notes


    - `PATCH /hub/agent-session-visibility/{session_id}` — the handler reads the
    path parameter as `x-param-session_id`, matching its sibling `PATCH
    /hub/agent-session/{session_id}`.

    - `GET|POST|PUT /hub/agent/user-context/{id}` — the handler requires the
    **agent id** as `x-param-id`; the frontend calls
    `/hub/agent/user-context/<agentId>`.
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Skills
  - name: Todos
  - name: Memory
  - name: Profile and personality
  - name: Corrections
  - name: Environment
  - name: Models
paths:
  /hub/coworker/task-space:
    put:
      tags:
        - Todos
      summary: Set the default space for promoted tasks
      description: >-
        **Account admins only** — this moves where *every* member's promotions
        and every task Abbie creates herself end up.


        `space_id` is required (an omitted field is a 400, never a silent reset;
        send `ESCALATE` explicitly to return to the built-in default), is
        uppercased, and is **validated against the account's real spaces before
        it is stored** — an unvalidated id would sit in the aggregate looking
        fine and fail on every future promotion. `ESCALATE` is accepted without
        a lookup because workspaces-service hardcodes it rather than storing it.


        An unknown space is 400; a failed space lookup is 502. Subject:
        `microstrate.hub.put.coworker-task-space`.
      operationId: putCoworkerTaskSpace
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - space_id
              properties:
                space_id:
                  type: string
                  example: ESCALATE
      responses:
        '200':
          description: The setting as stored
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TaskSpaceSetting'
        '400':
          description: >-
            Missing/blank `space_id`, or a space id that names no space on this
            account
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/AdminOnly'
        '502':
          description: >-
            The account's space list could not be read, or the role lookup
            failed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    TaskSpaceSetting:
      type: object
      properties:
        space_id:
          type: string
          description: >-
            Always uppercase and never empty; `ESCALATE` when the account has
            never chosen
          example: ESCALATE
        updated:
          type: string
          format: date-time
          description: >-
            Its **absence** means the account has never chosen and is inheriting
            the built-in default
    Error:
      type: object
      description: The unwrapped error body. The HTTP status carries the code.
      properties:
        error:
          type: string
      required:
        - error
  responses:
    Unauthorized:
      description: No account (or user) identity in the auth context
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    AdminOnly:
      description: An account admin role is required
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.