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

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.

​
term_id
integer
required

The unique identifier of the term. This must be a positive integer that corresponds to an existing term in the system.

Required range: x > 0

Body

application/json

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.

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