> ## Documentation Index > Fetch the complete documentation index at: https://docs.talqui.chat/llms.txt > Use this file to discover all available pages before exploring further. # Upsert reasoning settings > Changes who may see the reasoning behind automated messages. Only owners and superusers may change it; the stored audience is kept when the body sends only the toggle. ## OpenAPI ````yaml /api/services-api.yaml put /v1/tenants/{tenantID}/settings/reasoning openapi: 3.0.3 info: description: >- Talqui is an omnichannel customer service platform that unifies conversations from WhatsApp, Instagram, Telegram, and many other channels into a single attendant panel, alongside a broader ecosystem of plugins and integrations. This API gives developers programmatic access to Talqui's services layer, exposing the operations needed to read and manage tenants, conversations, plugins, and related resources that power that platform. Authentication is available on behalf of an Operator (the default for this API), a Plugin Connection, or a Plugin — see the [Talqui authentication guide](https://docs.talqui.chat/guides/introduction/authentication/) for how each token is obtained and when to use it. Need help or have questions not covered here? Reach out to support@talqui.com. license: name: ISC url: https://opensource.org/license/isc-license-txt title: Talqui - Services API version: 0.69.1 servers: - description: Production url: https://services-api.talqui.chat security: [] tags: - name: Tenants - name: Settings - name: Analytics/Reports - name: Analytics - name: Campaigns - name: Campaigns/Models - name: Contacts - name: Contacts/Imports - name: Handoff links - name: Inboxes - name: Messages - name: Notifications - name: Sessions - name: Operators/Shortcuts - name: Operators - name: Plugins - name: Setup - name: Uploads paths: /v1/tenants/{tenantID}/settings/reasoning: put: tags: - Settings summary: Upsert reasoning settings description: >- Changes who may see the reasoning behind automated messages. Only owners and superusers may change it; the stored audience is kept when the body sends only the toggle. operationId: UpsertReasoningSettingsController parameters: - in: path name: tenantID required: true schema: description: The tenant whose reasoning settings are changed. format: uuid pattern: >- ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$ type: string requestBody: content: application/json: schema: properties: settings: properties: reasoningDisplayAudience: description: Who may see it. Omitted keeps the stored audience. enum: - owners - managers - everyone type: string reasoningDisplayEnabled: description: Turns the reasoning display on or off. type: boolean required: - reasoningDisplayEnabled type: object required: - settings type: object required: true responses: '200': content: application/json: schema: additionalProperties: false properties: requester: additionalProperties: false description: >- Present when the caller is an operator; null for plugin and plugin-connection callers. nullable: true properties: canEdit: description: >- Whether the caller may change these settings (owners and superusers). type: boolean canView: description: >- Whether the caller may see the reasoning under the current settings. type: boolean operatorRole: description: Role of the caller in this tenant. enum: - operator - manager - owner - superuser type: string required: - operatorRole - canView - canEdit type: object settings: additionalProperties: false properties: reasoningDisplayAudience: description: >- Who may see it once enabled: owners, owners and managers, or every operator. enum: - owners - managers - everyone type: string reasoningDisplayEnabled: description: >- Whether the reasoning behind automated messages is shown at all. type: boolean required: - reasoningDisplayEnabled - reasoningDisplayAudience type: object required: - settings - requester type: object description: Response for status 200. '400': content: application/json: schema: properties: errors: items: oneOf: - $ref: '#/components/schemas/MissingTenantIDError' - $ref: '#/components/schemas/RequestValidationError' maxItems: 1 minItems: 1 type: array required: - errors type: object description: >- MissingTenantIDError (error_code 1001): tenantID absent from the URL. | RequestValidationError (error_code 1002): request body fails schema validation. '401': content: application/json: schema: properties: errors: items: $ref: '#/components/schemas/UnauthorizedError' maxItems: 1 minItems: 1 type: array required: - errors type: object description: 'UnauthorizedError (error_code 1003): missing/invalid operator token.' '403': content: application/json: schema: properties: errors: items: $ref: '#/components/schemas/ForbiddenError' maxItems: 1 minItems: 1 type: array required: - errors type: object description: >- ForbiddenError (error_code 1004): operator is not an owner or superuser of this tenant. '404': content: application/json: schema: properties: errors: items: $ref: '#/components/schemas/TenantNotFoundError' maxItems: 1 minItems: 1 type: array required: - errors type: object description: >- TenantNotFoundError (error_code 1062): tenant does not exist or was deleted. '500': content: application/json: schema: properties: errors: items: $ref: '#/components/schemas/UnknownError' maxItems: 1 minItems: 1 type: array required: - errors type: object description: >- UnknownError (error_code 5999): Unexpected internal error not otherwise documented for this endpoint. components: schemas: MissingTenantIDError: additionalProperties: false properties: error: enum: - MissingTenantIDError type: string error_code: enum: - 1001 type: number message: example: tenantID is required. type: string statusCode: enum: - 400 type: number required: - statusCode - error - error_code - message type: object RequestValidationError: additionalProperties: false properties: error: enum: - RequestValidationError type: string error_code: enum: - 1002 type: number fields: items: additionalProperties: false properties: allowed: type: string field: type: string received: type: string required: - field - received - allowed type: object type: array message: example: Invalid request data. type: string statusCode: enum: - 400 type: number required: - statusCode - error - error_code - message - fields type: object UnauthorizedError: additionalProperties: false properties: error: enum: - UnauthorizedError type: string error_code: enum: - 1003 type: number message: example: You are not authorized to perform this request. type: string statusCode: enum: - 401 type: number required: - statusCode - error - error_code - message type: object ForbiddenError: additionalProperties: false properties: error: enum: - ForbiddenError type: string error_code: enum: - 1004 type: number message: example: You do not have access to this resource. type: string statusCode: enum: - 403 type: number required: - statusCode - error - error_code - message type: object TenantNotFoundError: additionalProperties: false properties: error: enum: - TenantNotFoundError type: string error_code: enum: - 1062 type: number message: example: Tenant not found. type: string statusCode: enum: - 404 type: number required: - statusCode - error - error_code - message type: object UnknownError: additionalProperties: false properties: error: enum: - UnknownError type: string error_code: enum: - 5999 type: number message: example: For some unknown reason your request has not succeeded. type: string statusCode: enum: - 500 type: number required: - statusCode - error - error_code - message type: object ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.