> ## 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.

# Add Term to Dictionary

> Adds a new term and its translations to an existing dictionary, enabling you to expand your multilingual terminology database with precise linguistic mappings.

This endpoint serves as your gateway to enriching dictionaries with new linguistic content. When you need to expand a dictionary's vocabulary, whether you're building a comprehensive translation resource or maintaining specialized terminology for your domain, this endpoint provides the mechanism to seamlessly add term-translation pairs that enhance your multilingual capabilities.
Think of this process as carefully placing a new entry into a physical dictionary, but with the added power of digital precision and immediate availability across all your applications. Each term you add becomes instantly searchable and usable through other dictionary endpoints, creating a growing repository of linguistic knowledge that serves your users' translation and terminology needs.

## The Update-Centric Approach

Notice that the operation summary describes this as "Update Term Translation In Dictionary Using Term ID" rather than simply "Add Term." This distinction reveals important architectural decisions about how the system handles dictionary content. Rather than treating each operation as creating entirely new database records, the system views term additions as updates to existing term structures.
This approach offers several advantages for dictionary management. It allows for versioning of translations, supports scenarios where terms need refinement over time, and provides mechanisms for tracking the evolution of linguistic content. When you "add" a term, you might actually be adding a new translation variant to an existing term concept, or updating existing translations with improved accuracy.

## Quality Considerations for Translation Content

Adding terms to dictionaries involves inherent quality considerations that go beyond technical correctness. Translation accuracy, cultural appropriateness, and consistency with existing dictionary content all influence the long-term value of your linguistic resources.
When designing term addition workflows, consider implementing validation steps that help ensure translation quality. This might involve requiring multiple translation variants, providing fields for usage examples or context information, or implementing review processes where translation additions require approval before becoming available to end users.


## OpenAPI

````yaml post /dictionaries/{dictionary_id}/add-term
openapi: 3.1.0
info:
  title: FastAPI
  version: 0.1.0
servers:
  - url: https://client.camb.ai/apis
security: []
paths:
  /dictionaries/{dictionary_id}/add-term:
    post:
      tags:
        - Apis
        - Dictionaries
      summary: Add Term To Dictionary
      operationId: add_term_to_dictionary_dictionaries__dictionary_id__add_term_post
      parameters:
        - name: dictionary_id
          in: path
          required: true
          schema:
            $ref: '#/components/schemas/DictionaryIDPathParam'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AddDictionaryTermPayload'
      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.
    AddDictionaryTermPayload:
      properties:
        translations:
          items:
            $ref: '#/components/schemas/TermTranslation'
          type: array
          title: Translations
      type: object
      description: >-
        Represents the payload used to add one or more translations for a given
        term. This object contains an array of 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.
      required:
        - translations
      title: AddDictionaryTermPayload
    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.

````