> ## 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.

# Remove an environment variable

> The key travels as `?key=KEY`, with a `key` field in the body as a fallback — a request body on DELETE does not survive every gateway intact.

A real removal, no tombstone. 404s when the key is not declared in **this** scope: quietly falling through to the org aggregate would let any member delete a variable the admin gate exists to protect.

Deliberately does **not** run aggregate validation — a delete can only shrink the document, and validating would make an entry that later rules grew to reject impossible to remove. Subject: `microstrate.hub.delete.coworker-env`.



## OpenAPI

````yaml /api-reference/endpoint/abbie/openapi.json delete /hub/coworker/env
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/env:
    delete:
      tags:
        - Environment
      summary: Remove an environment variable
      description: >-
        The key travels as `?key=KEY`, with a `key` field in the body as a
        fallback — a request body on DELETE does not survive every gateway
        intact.


        A real removal, no tombstone. 404s when the key is not declared in
        **this** scope: quietly falling through to the org aggregate would let
        any member delete a variable the admin gate exists to protect.


        Deliberately does **not** run aggregate validation — a delete can only
        shrink the document, and validating would make an entry that later rules
        grew to reject impossible to remove. Subject:
        `microstrate.hub.delete.coworker-env`.
      operationId: deleteCoworkerEnv
      parameters:
        - $ref: '#/components/parameters/EnvScope'
        - name: key
          in: query
          required: false
          description: >-
            Variable name. Required unless supplied in the body. Forwarded as
            `x-param-query-key`.
          schema:
            type: string
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                key:
                  type: string
      responses:
        '200':
          description: Deletion confirmation
          content:
            application/json:
              schema:
                type: object
                properties:
                  key:
                    type: string
                  scope:
                    type: string
                    enum:
                      - organisation
                      - user
                  deleted:
                    type: boolean
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/AdminOnly'
        '404':
          description: No such key declared in this scope
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '502':
          $ref: '#/components/responses/UpstreamError'
components:
  parameters:
    EnvScope:
      name: scope
      in: query
      required: false
      description: >-
        `user` addresses the caller's personal manifest; anything else —
        including an unrecognised value — resolves to organisation. A `user`
        request from a token that carries no user identity is a **400**, never
        widened to the organisation. Forwarded as `x-param-query-scope`.
      schema:
        type: string
        enum:
          - organisation
          - user
        default: organisation
  responses:
    BadRequest:
      description: Malformed payload or a failed validation rule
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    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'
    UpstreamError:
      description: >-
        A backend read or write failed — deliberately not degraded to an empty
        or default answer
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      description: The unwrapped error body. The HTTP status carries the code.
      properties:
        error:
          type: string
      required:
        - 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.