> ## Documentation Index > Fetch the complete documentation index at: https://developers.deepl.com/llms.txt > Use this file to discover all available pages before exploring further. # Check usage and limits ## OpenAPI ````yaml get /v2/usage openapi: 3.0.3 info: title: DeepL API Documentation description: >- The DeepL API provides programmatic access to DeepL’s language AI technology. Note: this OpenAPI spec is embedded into our API documentation and has shortened descriptions. termsOfService: https://www.deepl.com/pro-license contact: name: DeepL - Contact us url: https://www.deepl.com/contact-us version: 3.9.0 servers: - url: https://api.deepl.com description: DeepL API Pro - url: https://api-free.deepl.com description: DeepL API Free security: [] tags: - name: beta description: >- Experimental features that are under testing and not yet intended for production use. - name: TranslateText description: >- The text-translation API currently consists of a single endpoint, `translate`, which is described below. - name: TranslateDocuments description: >- The document translation API allows you to translate whole documents and supports the following file types and extensions: * `docx` - Microsoft Word Document * `pptx` - Microsoft PowerPoint Document * `xlsx` - Microsoft Excel Document * `pdf` - Portable Document Format * `htm / html` - HTML Document * `txt` - Plain Text Document * `xlf / xliff` - XLIFF Document, version 2.1 * `srt` - SRT Document * `jpeg` / `jpg` / `png` - Image (currently in beta) - name: RephraseText description: >- The `rephrase` endpoint is used to make corrections and adjustments to texts based on style or tone. - name: ManageMultilingualGlossaries description: >- The *glossary* functions allow you to create, inspect, edit and delete glossaries. Glossaries created with the glossary function can be used in translate requests by specifying the `glossary_id` parameter. A glossary contains (several) dictionaries. A dictionary is a mapping of source phrases to target phrases for a single language pair. If you encounter issues, please let us know at support@DeepL.com. Currently you can create glossaries with any of the languages DeepL supports (with the exception of Thai). The maximum size limit for a glossary is 10 MiB = 10485760 bytes and each source/target text, as well as the name of the glossary, is limited to 1024 UTF-8 bytes. A total of 1000 glossaries are allowed per account. When creating a dictionary with target language `EN`, `PT`, or `ZH`, it's not necessary to specify a variant (e.g. `EN-US`, `EN-GB`, `PT-PT`, `PT-BR`, or `ZH-HANS`). Dictionaries with target language `EN` can be used in translations with either English variant. Similarly `PT`, and `ZH` dictionaries can be used in translations with their corresponding variants. (When you provide the ID of a glossary to a translation, the appropriate dictionary is automatically applied. Currently glossaries can not yet be used with source language detection.) Glossaries created via the DeepL API are now unified with glossaries created via the DeepL website and DeepL apps. Please only use the v3 glossary API in conjunction with multilingual or edited glossaries from the website. - name: ManageGlossaries description: >- Please note that this is the spec for the (old) v2 glossary endpoint. We recommend users switch to the newer v3 glossary endpoints, which support editability and multilinguality. The *glossary* functions allow you to create, inspect, and delete glossaries. Glossaries created with the glossary function can be used in translate requests by specifying the `glossary_id` parameter. If you encounter issues, please let us know at support@DeepL.com. Currently you can create glossaries with any of the languages DeepL supports (with the exception of Thai). - name: MetaInformation description: Information about API usage and value ranges - name: TranslationMemories description: >- The translation memory endpoints allow you to interact with your account's translation memories, used to store and reuse previously created translations. Translation memories can be used in text translation requests by specifying the `translation_memory_id` parameter to denote a specific translation memory and the `translation_memory_threshold` which defines the minimum matching percentage required for a translation memory segment to be applied (recommended to be 75% or higher). - name: VoiceAPI description: >- The Voice API provides real-time voice transcription and translation services. Use a two-step flow: first request a streaming URL via REST, then establish a WebSocket connection for streaming audio and receiving transcriptions. - name: VoiceTranslateJob description: >- **Alpha.** Async voice translation jobs. This API may change without notice. externalDocs: description: DeepL Pro - Plans and pricing url: https://www.deepl.com/pro#developer paths: /v2/usage: get: tags: - MetaInformation summary: Check Usage and Limits operationId: getUsage responses: '200': description: The account's usage and limits. headers: X-Trace-ID: $ref: '#/components/headers/X-Trace-ID' content: application/json: schema: $ref: '#/components/schemas/UsageResponse' examples: free: summary: Response for API users not on the Pro plan value: character_count: 180118 character_limit: 1250000 pro: summary: Response for API Pro users value: character_count: 5947223 character_limit: 1000000000000 products: - product_type: write billing_unit: characters api_key_unit_count: 0 account_unit_count: 5643 api_key_character_count: 0 character_count: 5643 - product_type: translate billing_unit: characters api_key_unit_count: 636 account_unit_count: 5941580 api_key_character_count: 636 character_count: 5941580 - product_type: speech_to_text billing_unit: milliseconds api_key_unit_count: 1800000 account_unit_count: 1800000 api_key_character_count: 0 character_count: 0 api_key_character_count: 636 api_key_character_limit: 1000000000000 speech_to_text_milliseconds_count: 1800000 speech_to_text_milliseconds_limit: 36000000 start_time: '2025-05-13T09:18:42Z' end_time: '2025-06-13T09:18:42Z' '400': $ref: '#/components/responses/BadRequest' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '413': $ref: '#/components/responses/PayloadTooLarge' '429': $ref: '#/components/responses/TooManyRequests' '456': $ref: '#/components/responses/QuotaExceeded' '500': $ref: '#/components/responses/InternalServerError' '504': $ref: '#/components/responses/ServiceUnavailable' '529': $ref: '#/components/responses/TooManyRequests' security: - auth_header: [] components: headers: X-Trace-ID: description: >- A unique identifier for the request that can be included in bug reports to DeepL support. schema: type: string example: 501c3d93cc0c4f11ae2f60a226c2f0f0 schemas: UsageResponse: type: object properties: character_count: description: Characters translated so far in the current billing period. type: integer format: int64 example: 180118 character_limit: description: >- Current maximum number of characters that can be translated per billing period. If cost control is set, the cost control limit will be returned in this field. type: integer format: int64 example: 1250000 products: type: array description: Only present for API Pro users. Per-product usage details. items: type: object properties: product_type: type: string description: The type of product (e.g., 'write', 'translate'). example: write billing_unit: type: string enum: - characters - milliseconds description: The billing unit for this product type. example: characters api_key_unit_count: type: integer description: >- Units used for this product by this API key in the current period. example: 0 account_unit_count: type: integer description: Total units used for this product in the current period. example: 5643 api_key_character_count: type: integer deprecated: true description: >- Use api_key_unit_count instead. Characters used for this product by this API key in the current period." example: 0 character_count: type: integer deprecated: true description: >- Use account_unit_count instead. Total characters used for this product in the current period." example: 5643 api_key_character_count: type: integer description: >- Only present for API Pro users. Total characters used by this API key in the current period. example: 636 api_key_character_limit: type: integer description: >- Only present for API Pro users. Character limit for this API key in the current period. example: 1000000000000 speech_to_text_milliseconds_count: type: integer description: >- Only present for API Pro users. Milliseconds of speech-to-text used in the current period. example: 1800000 speech_to_text_milliseconds_limit: type: integer description: >- Only present for API Pro users. Milliseconds of speech-to-text limit in the current period. example: 36000000 start_time: type: string format: date-time description: >- Only present for API Pro users. Start time of the current billing period (ISO 8601). example: '2025-05-13T09:18:42Z' end_time: type: string format: date-time description: >- Only present for API Pro users. End time of the current billing period (ISO 8601). example: '2025-06-13T09:18:42Z' responses: BadRequest: description: Bad request. Please check error message and your parameters. Forbidden: description: >- Authorization failed. Please supply a valid `DeepL-Auth-Key` via the `Authorization` header. NotFound: description: The requested resource could not be found. PayloadTooLarge: description: The request size exceeds the limit. TooManyRequests: description: Too many requests. Please wait and resend your request. QuotaExceeded: description: Quota exceeded. The character limit has been reached. InternalServerError: description: Internal error. ServiceUnavailable: description: Resource currently unavailable. Try again later. securitySchemes: auth_header: type: apiKey description: > Authentication with `Authorization` header and `DeepL-Auth-Key` authentication scheme. Example: `DeepL-Auth-Key ` name: Authorization in: header x-default: 'DeepL-Auth-Key ' ````