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

# Update Translation for a Term in Dictionary

> Updates existing translations for a specific term within a dictionary, allowing you to refine translation accuracy, add new language variants, or correct linguistic content as your understanding evolves.

This endpoint represents one of the most nuanced and powerful operations in dictionary management - the ability to refine and improve existing translations after they've been established. Unlike creating new terms or adding entirely new content, updating translations acknowledges that language is living and evolving, and that our understanding of how concepts translate across cultures deepens over time.

## Understanding the Evolution of Translation Quality

The need to update translations arises from several important realities of multilingual content management. Languages themselves evolve, with new terms entering common usage while others become obsolete. Technical domains introduce specialized vocabulary that requires increasingly precise translations as understanding deepens. Cultural contexts shift, making some translations more or less appropriate over time.

## Quality Assurance in Translation Updates

Updating translations carries inherent responsibilities around quality assurance that extend beyond technical correctness. When you modify existing translations, you're potentially affecting every user and system that depends on that linguistic mapping. This influence requires thoughtful consideration of how changes might impact existing workflows, cached content, or user expectations.

## Integration Strategies for Translation Management

Consider implementing interfaces that help users understand the context and impact of proposed translation changes. Showing how current translations are being used, what alternatives exist, or how changes might affect related terms helps users make informed decisions about when updates truly improve linguistic resources versus when they might cause unintended disruption.


## OpenAPI

````yaml put /dictionaries/term/{dictionary_id}/{term_id}
openapi: 3.1.0
info:
  title: FastAPI
  version: 0.1.0
servers:
  - url: https://client.camb.ai/apis
security: []
paths:
  /dictionaries/term/{dictionary_id}/{term_id}:
    put:
      tags:
        - Apis
        - Dictionaries
      summary: Update Term Translation In Dictionary Using Term Id
      operationId: >-
        update_term_translation_in_dictionary_using_term_id_dictionaries_term__dictionary_id___term_id__put
      parameters:
        - name: dictionary_id
          in: path
          required: true
          schema:
            $ref: '#/components/schemas/DictionaryIDPathParam'
        - name: term_id
          in: path
          required: true
          schema:
            type: integer
            exclusiveMinimum: 0
            title: Term Id
            description: >-
              The unique identifier of the term. This must be a positive integer
              that corresponds to an existing term in the system.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateTermTranslationsPayload'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DictionaryCreated'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
components:
  schemas:
    DictionaryIDPathParam:
      type: integer
      title: Dictionary Id
      description: >-
        This parameter tells the API exactly which dictionary you're interested
        in. Each dictionary in the system has a unique numerical ID that serves
        as its primary identifier.
    UpdateTermTranslationsPayload:
      properties:
        translations:
          items:
            $ref: '#/components/schemas/TermTranslation'
          type: array
          title: Translations
      description: >-
        Represents the payload used to update one or more translations for a
        given term. This object contains an array of TermTranslation entries,
        each specifying a translated text and its target language. When
        submitted, the existing set of translations for the term will be
        replaced or augmented according to the provided list.
      type: object
      required:
        - translations
      title: UpdateTermTranslationsPayload
    DictionaryCreated:
      properties:
        message:
          type: string
          title: Message
          description: >-
            Human-readable feedback that communicates the outcome of the
            dictionary operation with actionable context for your application
            users. This message provides essential information about operation
            success, partial completion scenarios, or guidance for addressing
            any issues that occurred during processing.
        status:
          type: string
          title: Status
          description: >-
            Standardized operation outcome indicator that enables programmatic
            response handling across all dictionary management workflows. This
            status field provides consistent, machine-readable confirmation of
            operation results, allowing your application logic to branch
            appropriately between success scenarios, partial completion cases,
            and error conditions.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    TermTranslation:
      properties:
        translation:
          type: string
          maxLength: 255
          title: Translation
          description: >-
            The translated text of the term in the specified target language.
            This should be the most accurate and contextually appropriate
            translation of the original term.
        language:
          $ref: '#/components/schemas/Languages'
          description: >-
            The target language for this translation. This determines the
            linguistic and cultural context in which the translation should be
            interpreted.
      type: object
      required:
        - translation
        - language
      title: TermTranslation
      description: >-
        Represents a single translation of a term into a specific target
        language. Each object contains the translated text along with its
        corresponding language identifier, enabling multilingual term management
        and localization workflows.
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
    Languages:
      type: integer
      enum:
        - 1
        - 2
        - 3
        - 4
        - 5
        - 6
        - 7
        - 8
        - 9
        - 10
        - 11
        - 12
        - 13
        - 14
        - 15
        - 16
        - 17
        - 18
        - 19
        - 20
        - 21
        - 22
        - 23
        - 24
        - 25
        - 26
        - 27
        - 28
        - 29
        - 30
        - 31
        - 32
        - 33
        - 34
        - 35
        - 36
        - 37
        - 38
        - 39
        - 40
        - 41
        - 42
        - 43
        - 44
        - 45
        - 46
        - 47
        - 48
        - 49
        - 50
        - 51
        - 52
        - 53
        - 54
        - 55
        - 56
        - 57
        - 58
        - 59
        - 60
        - 61
        - 62
        - 63
        - 64
        - 65
        - 66
        - 67
        - 68
        - 69
        - 70
        - 71
        - 72
        - 73
        - 74
        - 75
        - 76
        - 77
        - 78
        - 79
        - 80
        - 81
        - 82
        - 83
        - 84
        - 85
        - 86
        - 87
        - 88
        - 89
        - 90
        - 91
        - 92
        - 93
        - 94
        - 95
        - 96
        - 97
        - 98
        - 99
        - 100
        - 101
        - 102
        - 103
        - 104
        - 105
        - 106
        - 107
        - 108
        - 109
        - 110
        - 111
        - 112
        - 113
        - 114
        - 115
        - 116
        - 117
        - 118
        - 119
        - 120
        - 121
        - 122
        - 123
        - 124
        - 125
        - 126
        - 127
        - 128
        - 129
        - 130
        - 131
        - 132
        - 133
        - 134
        - 135
        - 136
        - 139
        - 140
        - 141
        - 142
        - 143
        - 144
        - 145
        - 146
        - 147
        - 148
        - 149
        - 150
      title: Languages
      default: 1
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        The `x-api-key` is a custom header required for authenticating requests
        to our API. Include this header in your request with the appropriate API
        key value to securely access our endpoints. You can find your API key(s)
        in the 'API' section of our studio website.

````