Skip to main content
DeepL offers several ways to retrieve usage data so you can track character and minute consumption and the associated costs. This guide compares the available data sources and shows how to use each one.
Consumption data in the account UI, in CSV exports, and in the Admin API analytics endpoints is available up to and including the previous UTC calendar day. For near-real-time data, use the /usage endpoint.

​
Choose a data source

Use the account UI for a quick check while signed in, the CSV export for detailed or offline analysis per key, per custom tag, or per language pair, the /usage endpoint for programmatic near-real-time quota checks, and the Admin API analytics endpoints for programmatic reporting and cost attribution.

​
API Keys and Limits tab

To check per-key consumption for the current monthly usage period, open the API Keys & Limits tab. It shows consumption for each API key in a single unit at a time — characters, speech-to-text (STT) minutes, or speech-to-speech (STS) minutes.

The API Keys & Limits tab

Use the unit dropdown above the key table to switch which usage unit the table displays.

Switching the displayed usage unit

​
API Usage tab

To check your account totals, open the API Usage tab. It shows total character and STT minute usage for the current monthly usage period, and if you’re on a yearly plan, usage to date for your yearly billing period, too.

The API Usage tab

​
CSV export

Generate a CSV report of your usage for a chosen time period. Three report types are available:
  • API key-level report: characters translated per API key, including a column that breaks out text improvement (Write API) characters separately. Key-level usage is not broken out on invoices; retrieve it via CSV export, the “API Keys & Limits” tab, or the Admin API analytics endpoints.
  • Custom tag-level report: characters translated per custom reporting tag. Only tagged requests appear in this report, so results reflect a subset of total usage unless every request is tagged.
  • Language pair-level report: characters translated per source-target language pair. Generally available on the API Enterprise plan. On the API Pro plan, it’s available on request; contact your customer success manager to enable it.
To download a report, click “Download CSV usage report” on the API Keys & Limits tab or the API Usage tab and select “API key-level report,” “Custom tag-level report,” or “Language pair-level report” from the dropdown. Then select a time period and click “Download your report”.

Select a report type from the "Download CSV usage report" dropdown

Select a custom date range of up to 4 months (on UTC calendar days) or one of the presets, which cover rolling windows from the last 24 hours up to the last year as well as calendar months and usage periods. Rolling presets include the current day; calendar-month and usage-period ranges align to UTC day or period boundaries, so they might not start and end on a full calendar day. For any time range, you can also group usage data by UTC calendar day:

Select the "Group by day" option to group usage data by UTC calendar day

Document translation data is only included in reports with a time period starting on or after May 16, 2024 00:00 UTC. Text translation data is included for all time periods.

​
The usage endpoint

The /usage endpoint returns a near-real-time snapshot of character and minute usage in the current monthly usage period, typically up to date within a few minutes of the usage being generated. Use it for programmatic quota checks, for example before submitting a large translation batch.

​
Admin API analytics

The Admin API provides programmatic access to usage data over a custom date range, with optional grouping by day. It requires an admin key for authentication. Two endpoints are available:
  • Get usage analytics returns usage statistics across all services (text translation, document translation, text improvement, and speech-to-text), in total or grouped by API key
  • Get custom tag usage analytics returns usage broken down by custom tag
Custom tags are an optional dimension for cost attribution: attach a tag to individual API requests with the X-DeepL-Reporting-Tag header to track consumption by team, project, or any other category. Only tagged requests appear in custom-tag analytics, so results reflect a subset of total usage unless every request is tagged. See How to use custom reporting tags for setup and naming guidance. If you prefer a download over an API call, the same per-tag data is available as a custom tag-level CSV export. For a worked example of pulling analytics data into a dashboard, see the usage analytics dashboard cookbook.