# DeveloperKeys: DeepL Developer Keys ## Documentation The developer keys of the organisation; needs an admin key. A delete deactivates the key, permanently, and the key stays listed. - Catalog: `DeepL` - Schema: `Admin` - Primary Keys: `key_id` - Label: Developer Keys Can retrieve data and change data using insert, update and delete. ## Table Columns The columns of the table `DeveloperKeys` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `creation_time` | `datetime` | | ☐ | When the key was created (UTC). | | `deactivated_time` | `datetime` | | ☐ | When the key was deactivated (UTC). | | `is_deactivated` | `char` | | ☐ | Whether the key is deactivated; can only be set, never cleared. | | `key_id` | `varchar2` | | ☑ | The id of the key. | | `label` | `varchar2` | | ☐ | The label of the key. | | `usage_limit_characters` | `int64` | | ☐ | Monthly limit on characters over text, documents and improvement; 0 blocks, empty is no limit. | | `usage_limit_speech_to_text_ms` | `int64` | | ☐ | Monthly limit on milliseconds of speech to text; 0 blocks, empty is no limit. |