POST
/
dictionaries
/
{dictionary_id}
/
add-term
Add Term To Dictionary
curl --request POST \
  --url https://client.camb.ai/apis/dictionaries/{dictionary_id}/add-term \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "translations": [
    {
      "translation": "<string>",
      "language": 1
    }
  ]
}'
{
  "message": "<string>",
  "status": "<string>"
}
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.

Authorizations

​
x-api-key
string
header
required

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.

Path Parameters

​
dictionary_id
integer
required

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.

Body

application/json

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.

​
translations
TermTranslation · object[]
required

Response

Successful Response

​
message
string

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
string

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.