Localization

All user-facing text in the DTPR API is returned as locale arrays — arrays of objects containing a language code and the localized string value.

Locale array format

Every text field (titles, descriptions, prompts, labels, etc.) follows this pattern:

[
  { "locale": "en", "value": "Technology" },
  { "locale": "fr", "value": "Technologie" },
  { "locale": "es", "value": "Tecnolog\u00eda" }
]

Each object has:

• locale — A language or region code (e.g., en, fr, es, km, pt, tl, fr-CA)
• value — The localized text string

Available locales

The DTPR taxonomy currently includes content in these locales:

Filtering with the locales parameter

The v1 typed endpoints and every v2 read endpoint accept an optional locales query parameter. Base URL: https://api.dtpr.io.

GET /api/v1/elements/device?locales=en
GET /api/v1/elements/ai?locales=en,fr
GET /api/v1/categories/device?locales=en,es
GET /api/v2/schemas/{version}/elements?locales=en,fr

When provided, the API filters all locale arrays in the response to include only the requested locales. This affects:

• Element title, description, citation
• Element icon.alt_text
• Element variable label arrays
• Category name, description, prompt
• Category element_variables[].label arrays

When omitted, all available locales are returned.

Implementation notes

• Locale codes are matched exactly — en will not match en-US
• If a requested locale doesn't exist for a field, that field's array will be empty
• The locales parameter accepts a comma-separated list with no spaces