DeepL Admin API adds usage per language pair (November 13, 2026)
New GET /v2/admin/analytics/language-pairs returns usage per source and target language, by day or by API key. Enterprise plan.
What changed
DeepL added a new Admin API endpoint on November 13, 2026: GET /v2/admin/analytics/language-pairs. It returns your API usage for each source and target language pair, which is useful for dashboards and cost reports.
Query parameters, from the API reference:
start_date(required): ISO 8601 date, read as UTC. It cannot be after the current UTC day or more than 63 days before it.end_date(required): ISO 8601 date, read as UTC. Data exists up to and including the previous UTC day.aggregate_by:period(default, totals for the range) orday(one row per UTC day).group_by:keyis the only supported value. It splits each language pair by API key.page: the page number to return. Pass thenext_pagevalue from the previous response.next_pageisnullon the last page.
The response is a language_pair_usage_report object with a language_pair_usages array. Each entry has source_language, target_language and a usage object with total_characters, text_translation_characters, document_translation_characters, text_improvement_characters, speech_to_text_minutes and speech_to_speech_minutes. Voice minutes are not counted in total_characters.
With group_by=key each entry also has api_key (masked) and api_key_label. With aggregate_by=day each entry also has usage_date. Usage from keys that are no longer on the account comes back with api_key set to - and api_key_label set to unknown.
The data is generally available on the API Enterprise plan. On API Pro it is available on request through your customer success manager. Accounts without the data get a successful response with an empty language_pair_usages array, not an error.
What to do
Call the endpoint with an admin key in the header . Admin keys are created in the "Admin API Keys" tab of your DeepL account. A normal developer key cannot call the Admin API.
