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

# Read who changed a project's settings, and to what

> Every save made to this project's settings, newest first, with the value on each side of each change — which is how a change is undone: patch the field back to its `before`. Filtered by the same permissions as getProjectSettings, so a save that touched a field you cannot read is still listed but shows only the changes you can see. Pass `field` to follow a single setting's whole history.



## OpenAPI

````yaml /api-reference/specs/claudia/v1.json get /v1/projects/{project}/settings/history
openapi: 3.0.1
info:
  title: Claudia API
  version: 1.0.0
servers:
  - url: https://api.cloudhumans.com/claudia
    description: Production
  - url: https://api.cloudhumans.com/claudia/staging
    description: Staging
security:
  - bearerAuth: []
tags:
  - name: MCP Servers
    description: >-
      The MCP servers your agents can call tools on. Registering one here is
      what makes its tools selectable in an agent; the credentials it needs are
      stored encrypted and never read back.
  - name: Knowledge Base Content
    description: Read, search and edit the content that answers your customers.
  - name: Content Quality
    description: Rewrites proposed for content that is answering your customers badly.
  - name: Playground
    description: >-
      Talk to one of your agents as if you were a customer, without touching a
      real conversation.
  - name: Project Settings
    description: >-
      Read and change how a ClaudIA project behaves — the settings screens of
      the ClaudIA app, as an API.
  - name: Content Improvements
    description: Answers Claudia proposes for questions your content does not cover yet.
  - name: Knowledge Bases
    description: The knowledge bases your account can manage.
  - name: Content Sources
    description: The sites Claudia crawls to keep a knowledge base in sync.
paths:
  /v1/projects/{project}/settings/history:
    get:
      tags:
        - Project Settings
      summary: Read who changed a project's settings, and to what
      description: >-
        Every save made to this project's settings, newest first, with the value
        on each side of each change — which is how a change is undone: patch the
        field back to its `before`. Filtered by the same permissions as
        getProjectSettings, so a save that touched a field you cannot read is
        still listed but shows only the changes you can see. Pass `field` to
        follow a single setting's whole history.
      operationId: getProjectSettingsHistory
      parameters:
        - name: project
          in: path
          description: >-
            The ClaudIA project to act on, by name. Get the names from
            listMyClaudiaProjects — a project these credentials do not cover
            answers 404, indistinguishable from one that does not exist.
          required: true
          schema:
            type: string
        - name: accountId
          in: query
          description: >-
            The CloudChat account whose permissions decide what you may read and
            write here, e.g. `7`. It is permission context, not the resource:
            the project is named in the path. Only unique within an instance, so
            it is always read together with the `cloudchat-instance` header —
            get the pair from listMyCloudChatAccounts. An account your
            credentials hold no editing claim for answers 403.
          required: true
          schema:
            type: string
        - name: cloudchat-instance
          in: header
          description: >-
            The CloudChat instance the account lives in, e.g. `4`. Sent as a
            header, and required: with `accountId` it forms the pair that names
            exactly one account, which `accountId` alone does not.
            listMyCloudChatAccounts returns the value to send here alongside
            each accountId.
          required: true
          schema:
            type: string
        - name: field
          in: query
          description: >-
            Follow one setting only, by its dotted path as getProjectSettings
            spells it (`greetingsSettings.staticGreeting`). A field you are not
            allowed to read is refused rather than answered empty. Omit to read
            every setting's history.
          required: false
          schema:
            type: string
          example: greetingsSettings.staticGreeting
        - name: page
          in: query
          description: Page index, newest first. Page with `hasMore` from the response.
          required: false
          schema:
            type: integer
            format: int32
            default: 0
          example: 0
        - name: size
          in: query
          description: Page size. Capped at 100.
          required: false
          schema:
            type: integer
            format: int32
            default: 20
          example: 20
      responses:
        '200':
          description: One page of saves.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProjectSettingsHistoryPage'
        '400':
          description: The request could not be answered as written.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Missing, expired or invalid credentials.
        '403':
          description: The credentials hold no account allowed to manage this content.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: >-
            No such resource, or none these credentials can reach — the two are
            deliberately indistinguishable.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: Rate limit applied by the API gateway. Back off and retry.
        '503':
          description: >-
            CloudChat could not be reached to resolve what this role may read,
            so no history is returned.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    ProjectSettingsHistoryPage:
      required:
        - hasMore
        - items
        - page
        - size
      type: object
      properties:
        items:
          type: array
          description: The saves on this page.
          items:
            $ref: '#/components/schemas/ProjectSettingsHistoryEntry'
        page:
          type: integer
          description: Page index this page was read at.
          format: int32
          example: 0
        size:
          type: integer
          description: Page size actually applied (capped at 100).
          format: int32
          example: 20
        hasMore:
          type: boolean
          description: Whether another page follows.
          example: false
      description: One page of saves, newest first.
    Error:
      required:
        - error
      type: object
      properties:
        error:
          type: string
          description: What went wrong.
          example: 'Forbidden: token holds no claim for the requested account'
      description: Something the caller needs to fix.
    ProjectSettingsHistoryEntry:
      required:
        - changedAt
        - changedBy
        - changes
      type: object
      properties:
        id:
          type: string
          description: Identifies this entry.
          example: 6683f1c2a4b19e0012ab34cd
        changedBy:
          type: string
          description: Who saved it.
          example: someone@acme.com
        changedAt:
          type: string
          description: When it was saved (ISO-8601).
          example: '2026-08-10T18:20:41'
        changes:
          type: array
          description: >-
            The fields this save changed, already filtered to the ones you may
            read: a save that also touched fields outside your permissions is
            still listed, carrying only the changes you can see.
          items:
            $ref: '#/components/schemas/ProjectSettingsChange'
      description: >-
        One save, and every field it changed. A save that touched several fields
        is one entry carrying several changes — which is what makes it a
        rollback unit: to undo a save, patch each change back to its `before`.
    ProjectSettingsChange:
      required:
        - path
      type: object
      properties:
        path:
          type: string
          description: The dotted path that changed.
          example: greetingsSettings.staticGreetingEnabled
        before:
          type: object
          description: >-
            The value before the change. Null both when it was null and when the
            field was unset.
        after:
          type: object
          description: The value after the change.
      description: One field that changed, with the values on either side of the change.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````