> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-hidden-info-by-role.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Finding Settings

> Enable or disable detection for one or more finding types in a single
 write. Enabling a type whose detector is a scheduled job also queues an
 immediate run.



## OpenAPI

````yaml https://spec.speakeasy.com/conductor-one/conductorone/my-source-with-code-samples post /api/v1/findings/settings/update
openapi: 3.1.0
info:
  description: The C1 API is a HTTP API for managing C1 resources.
  title: C1 API
  version: 0.1.0-alpha
servers:
  - description: The C1 API server for the current tenant.
    url: https://{tenantDomain}.conductor.one
    variables:
      tenantDomain:
        default: example
        description: The domain of the tenant to use for this request.
security:
  - bearerAuth: []
    oauth: []
paths:
  /api/v1/findings/settings/update:
    post:
      tags:
        - Finding Settings
      summary: Update Finding Settings
      description: |-
        Enable or disable detection for one or more finding types in a single
         write. Enabling a type whose detector is a scheduled job also queues an
         immediate run.
      operationId: c1.api.finding.v1.FindingSettingsService.UpdateFindingSettings
      requestBody:
        content:
          application/json:
            schema:
              $ref: >-
                #/components/schemas/c1.api.finding.v1.UpdateFindingSettingsRequest
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/c1.api.finding.v1.UpdateFindingSettingsResponse
          description: Successful response
components:
  schemas:
    c1.api.finding.v1.UpdateFindingSettingsRequest:
      description: The UpdateFindingSettingsRequest message.
      properties:
        settings:
          description: >-
            Applied as one atomic write, so an admin changing several types
            either
             lands all of them or none.
          items:
            $ref: '#/components/schemas/c1.api.finding.v1.FindingSettingsEntry'
          type:
            - array
            - 'null'
      title: Update Finding Settings Request
      type: object
      x-speakeasy-name-override: UpdateFindingSettingsRequest
    c1.api.finding.v1.UpdateFindingSettingsResponse:
      description: The UpdateFindingSettingsResponse message.
      properties:
        list:
          description: >-
            The full catalog after the write, in the same shape
            ListFindingSettings
             returns.
          items:
            $ref: '#/components/schemas/c1.api.finding.v1.FindingTypeSetting'
          type:
            - array
            - 'null'
      title: Update Finding Settings Response
      type: object
      x-speakeasy-name-override: UpdateFindingSettingsResponse
    c1.api.finding.v1.FindingSettingsEntry:
      description: >-
        FindingSettingsEntry is a requested change to one type, which is why it
        is a
         separate message from FindingTypeSetting rather than the same one reused: an
         update needs enum validation and presence on `enabled` so an omitted field is
         an error, while a response always carries a value and must not make callers
         handle an absent one.
      properties:
        enabled:
          description: >-
            Target state. Required: explicit presence keeps an omitted field
            from
             reading as false and silently switching a detector off.
          type:
            - boolean
            - 'null'
        findingType:
          description: The finding type to configure. Must be a detector-backed type.
          enum:
            - FINDING_TYPE_UNSPECIFIED
            - FINDING_TYPE_SIMILAR_USERNAME_MATCH
            - FINDING_TYPE_SERVICE_ACCOUNT_MISCLASSIFICATION
            - FINDING_TYPE_NHI_UNOWNED
            - FINDING_TYPE_SERVICE_ACCOUNT_UNOWNED
            - FINDING_TYPE_DECOY_CREDENTIAL_USED
            - FINDING_TYPE_CUSTOM
            - FINDING_TYPE_CONNECTOR_ANOMALY_DETECTION_DISABLED
            - FINDING_TYPE_DEACTIVATED_OWNER
            - FINDING_TYPE_UNUSED_SECRET
            - FINDING_TYPE_CREDENTIAL_PUBLICLY_EXPOSED
            - FINDING_TYPE_DECOY_PUBLICLY_EXPOSED
          type: string
          x-speakeasy-unknown-values: allow
      title: Finding Settings Entry
      type: object
      x-speakeasy-name-override: FindingSettingsEntry
    c1.api.finding.v1.FindingTypeSetting:
      description: >-
        FindingTypeSetting is one finding type's detection switch as it
        currently
         stands. Named for a single type on purpose: the stored model
         c1.models.finding.v1.FindingSettings is the tenant-wide object holding every
         type, and one name for both granularities reads as the same thing twice.
         Display copy for the type is client-owned; this carries state only.
      properties:
        enabled:
          description: >-
            Whether the system detects this finding type. Types never configured
            read
             back their shipped default, which is per type rather than uniformly on.
          type: boolean
        findingType:
          description: The findingType field.
          enum:
            - FINDING_TYPE_UNSPECIFIED
            - FINDING_TYPE_SIMILAR_USERNAME_MATCH
            - FINDING_TYPE_SERVICE_ACCOUNT_MISCLASSIFICATION
            - FINDING_TYPE_NHI_UNOWNED
            - FINDING_TYPE_SERVICE_ACCOUNT_UNOWNED
            - FINDING_TYPE_DECOY_CREDENTIAL_USED
            - FINDING_TYPE_CUSTOM
            - FINDING_TYPE_CONNECTOR_ANOMALY_DETECTION_DISABLED
            - FINDING_TYPE_DEACTIVATED_OWNER
            - FINDING_TYPE_UNUSED_SECRET
            - FINDING_TYPE_CREDENTIAL_PUBLICLY_EXPOSED
            - FINDING_TYPE_DECOY_PUBLICLY_EXPOSED
          type: string
          x-speakeasy-unknown-values: allow
      title: Finding Type Setting
      type: object
      x-speakeasy-name-override: FindingTypeSetting
  securitySchemes:
    bearerAuth:
      scheme: bearer
      type: http
    oauth:
      description: >-
        This API uses OAuth2 with the Client Credential flow.

        Client Credentials must be sent in the BODY, not the headers.

        For an example of how to implement this, refer to the
        [c1TokenSource.Token()](https://github.com/ConductorOne/conductorone-sdk-go/blob/3375fe7c0126d17e7ec4e711693dee7b791023aa/token_source.go#L101-L187)
        function.
      flows:
        clientCredentials:
          scopes: {}
          tokenUrl: /auth/v1/token
      type: oauth2

````