> ## Documentation Index > Fetch the complete documentation index at: https://docs.attention.com/llms.txt > Use this file to discover all available pages before exploring further. # Update Field Configuration > Partially updates a field configuration. Only properties present on the body are modified (PATCH semantics). Field configurations belonging to other organizations return 404. ## OpenAPI ````yaml patch /field-configurations/{id} openapi: 3.0.1 info: title: Attention Service V2 description: Attention Service API V2 termsOfService: https://www.attention.com/terms-of-use contact: name: Attention Team url: https://docs.attention.com/welcome email: support@attention.com license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html version: 1.8.0 servers: - url: https://api.attention.tech/v2 security: - APIKeyHeader: [] paths: /field-configurations/{id}: patch: tags: - Field Configuration summary: Update Field Configuration description: >- Partially updates a field configuration. Only properties present on the body are modified (PATCH semantics). Field configurations belonging to other organizations return 404. operationId: updateFieldConfiguration parameters: - name: id in: path description: UUID of the field configuration. required: true schema: type: string requestBody: description: Fields to update on the configuration. content: application/json: schema: $ref: '#/components/schemas/UpdateFieldConfigurationRequest' application/vnd.api+json: schema: $ref: '#/components/schemas/UpdateFieldConfigurationRequest' required: true responses: '200': description: Field configuration successfully updated. content: application/json: schema: $ref: '#/components/schemas/FieldConfigurationResponse' application/vnd.api+json: schema: $ref: '#/components/schemas/FieldConfigurationResponse' '400': description: Invalid body parameters or nothing mutable supplied. content: application/json: schema: $ref: '#/components/schemas/Error' application/vnd.api+json: schema: $ref: '#/components/schemas/Error' '401': description: Authentication failed. Please provide a valid API key. content: application/json: schema: $ref: '#/components/schemas/Error' application/vnd.api+json: schema: $ref: '#/components/schemas/Error' '404': description: >- No field configuration with the provided UUID exists in the organization. content: application/json: schema: $ref: '#/components/schemas/Error' application/vnd.api+json: schema: $ref: '#/components/schemas/Error' '409': description: >- A field configuration with the same name already exists in the organization. content: application/json: schema: $ref: '#/components/schemas/Error' application/vnd.api+json: schema: $ref: '#/components/schemas/Error' '422': description: >- Schema-level validation failure on the request body (e.g. value outside the allowed length range). content: application/json: schema: $ref: '#/components/schemas/Error' application/vnd.api+json: schema: $ref: '#/components/schemas/Error' default: description: Unexpected error. content: application/json: schema: $ref: '#/components/schemas/Error' application/vnd.api+json: schema: $ref: '#/components/schemas/Error' components: schemas: UpdateFieldConfigurationRequest: type: object properties: name: type: string description: New human-readable name. When present, trimmed; 1-128 characters. example: Renamed Discovery Questions teamsUUID: type: array description: >- Replacement list of team UUIDs this configuration is assigned to. When omitted, existing assignments are preserved. example: - fe515723-fe2e-4959-a5fa-c4d3937fe7e4 items: type: string allTeams: type: boolean description: >- When present, sets whether the configuration applies to every team in the organization. nullable: true example: false criteria: $ref: '#/components/schemas/FieldConfigurationCriteria' description: >- Request payload for updating a field configuration. Uses PATCH semantics - only fields present in the body are updated; omitted fields are left unchanged. example: name: Renamed Discovery Questions teamsUUID: - fe515723-fe2e-4959-a5fa-c4d3937fe7e4 FieldConfigurationResponse: type: object properties: data: $ref: '#/components/schemas/FieldConfiguration' description: Envelope containing a single field configuration. example: data: uuid: b9e1c0a0-5a3d-4a9c-9b1e-2d6f4b7a1c11 name: Enterprise Discovery Questions organizationUUID: 16b78cec-82ef-46d2-8213-5d3bb7d2571c teamsUUID: - fe515723-fe2e-4959-a5fa-c4d3937fe7e4 allTeams: false isDefaultTemplate: false Error: type: object properties: id: type: string description: A unique identifier for the error. status: type: string description: >- The HTTP status code applicable to this problem, expressed as a string value. code: type: string description: An application-specific error code, expressed as a string value. title: type: string description: A short, human-readable summary of the problem. detail: type: string description: >- A human-readable explanation specific to this occurrence of the problem. source: type: object properties: pointer: type: string parameter: type: string meta: type: object properties: {} example: id: not_found_error status: '404' code: '404' title: Not Found Error detail: The requested resource was not found source: pointer: /data/attributes/id FieldConfigurationCriteria: type: object properties: conditions: type: array description: Ordered list of conditions to evaluate. items: $ref: '#/components/schemas/FieldConfigurationCriteriaCondition' operator: type: string description: Boolean operator used to combine the conditions. example: AND enum: - AND - OR description: >- Criteria expression that controls when this field configuration applies. Conditions are combined using the specified boolean operator. example: conditions: - field: account.industry value: technology operator: AND FieldConfiguration: required: - allTeams - createdAt - isDefaultTemplate - name - organizationUUID - teamsUUID - uuid type: object properties: uuid: type: string description: Unique identifier of the field configuration. example: b9e1c0a0-5a3d-4a9c-9b1e-2d6f4b7a1c11 name: type: string description: Human-readable name of the field configuration. example: Enterprise Discovery Questions organizationUUID: type: string description: UUID of the organization the field configuration belongs to. example: 16b78cec-82ef-46d2-8213-5d3bb7d2571c teamsUUID: type: array description: >- UUIDs of the teams this field configuration is assigned to. Ignored when `allTeams` is true. example: - fe515723-fe2e-4959-a5fa-c4d3937fe7e4 items: type: string allTeams: type: boolean description: >- When true, this configuration applies to every team in the organization and `teamsUUID` is ignored. example: false isDefaultTemplate: type: boolean description: Whether this configuration is the organization's default template. example: false criteria: $ref: '#/components/schemas/FieldConfigurationCriteria' createdAt: type: string description: Timestamp when the configuration was created. format: date-time example: '2026-03-01T12:00:00Z' description: >- A Field Configuration (internally `IntelligenceItemCollection`) groups a set of intelligence items that are surfaced together for the teams it is assigned to. Field Configurations are scoped to a single organization. example: uuid: b9e1c0a0-5a3d-4a9c-9b1e-2d6f4b7a1c11 name: Enterprise Discovery Questions organizationUUID: 16b78cec-82ef-46d2-8213-5d3bb7d2571c teamsUUID: - fe515723-fe2e-4959-a5fa-c4d3937fe7e4 allTeams: false isDefaultTemplate: false criteria: conditions: - field: account.industry value: technology operator: AND createdAt: '2026-03-01T12:00:00Z' FieldConfigurationCriteriaCondition: type: object properties: field: type: string description: Name of the field the condition applies to. example: account.industry value: type: string description: Value the field must match for this condition. example: technology description: >- A single condition within a field-configuration criteria expression. Conditions reference a field name and the value it must match for an intelligence item to apply. example: field: account.industry value: technology securitySchemes: APIKeyHeader: type: apiKey name: Authorization in: header ````