> ## Documentation Index > Fetch the complete documentation index at: https://docs.telepatia.ai/llms.txt > Use this file to discover all available pages before exploring further. # Regenerar la clave API de una cuenta de médico > Rota la clave API de una cuenta de médico, identificada por su `publicId` (`acc_*`) o `internalCode`. La clave anterior se revoca con una breve ventana de gracia; la nueva clave en texto plano se devuelve **una sola vez**: guárdala de forma segura. Limitado a una regeneración por cuenta cada 2 minutos (`429 rate_limit_exceeded`). ## OpenAPI ````yaml /es/scribe-api/openapi-institutional.json post /v1/institutional/accounts/{account_id}/api-keys/regenerate openapi: 3.1.0 info: title: Scribe Public API description: >- API REST externa para integración con la plataforma Telepatia. Autentíquese con claves API, establezca el contexto de consulta y consulte sesiones de scribe. version: 0.1.0 servers: - url: https://scribe-api.telepatia.ai description: Production security: - BearerAuth: [] paths: /v1/institutional/accounts/{account_id}/api-keys/regenerate: post: tags: - Institutional - Institutional summary: Regenerar la clave API de una cuenta de médico description: >- Rota la clave API de una cuenta de médico, identificada por su `publicId` (`acc_*`) o `internalCode`. La clave anterior se revoca con una breve ventana de gracia; la nueva clave en texto plano se devuelve **una sola vez**: guárdala de forma segura. Limitado a una regeneración por cuenta cada 2 minutos (`429 rate_limit_exceeded`). operationId: >- api_institutional_account_api_key_regenerated_v1_institutional_accounts__account_id__api_keys_regenerate_post parameters: - name: account_id in: path required: true schema: type: string title: Account Id requestBody: content: application/json: schema: anyOf: - $ref: '#/components/schemas/RegenerateApiKeyRequest' - type: 'null' title: Request example: validForDays: 365 responses: '200': description: Respuesta exitosa content: application/json: schema: $ref: '#/components/schemas/RegenerateApiKeyResponse' example: accountId: acc_a1b2c3d4e5f6g7h8 apiKey: expiresAt: '2027-01-15T10:30:00Z' id: ak_a1b2c3d4e5f6g7h8 mode: prod prefix: sk_prod_a1b2c3d4...e5f6 '401': description: No autorizado — clave API faltante o inválida. content: application/json: examples: authentication_required: summary: Invalid or missing API key value: error: type: authentication_error code: authentication_required message: Invalid API key. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Prohibido — la clave API no puede realizar esta operación. content: application/json: examples: permission_denied: summary: Caller lacks permission for this resource value: error: type: permission_error code: permission_denied message: You do not have permission to access this resource. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 permission_denied_role: summary: API key's account role is not allowed this operation value: error: type: permission_error code: permission_denied message: >- Your API key is not allowed to create accounts. Account creation requires an institutional API key; this key is scoped to a doctor account. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '404': description: No encontrado — el recurso solicitado no existe. content: application/json: examples: resource_not_found: summary: Resource not found value: error: type: invalid_request_error code: resource_not_found message: No session scribe found for the given consultation ID. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '409': description: Conflicto — el recurso ya existe o está en estado conflictivo. content: application/json: examples: resource_conflict: summary: Resource conflict value: error: type: invalid_request_error code: resource_conflict message: >- consultationInternalId is already in use by a different consultation. param: consultationInternalId requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Too Many Requests content: application/json: examples: rate_limit_exceeded: summary: Rate limit exceeded value: error: type: invalid_request_error code: rate_limit_exceeded message: Too many requests. Please wait before trying again. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' '503': description: Servicio no disponible — una dependencia externa no está disponible. content: application/json: examples: service_unavailable: summary: External service unavailable value: error: type: api_error code: service_unavailable message: >- The service is temporarily unavailable. Please try again later. requestId: 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 schema: $ref: '#/components/schemas/ErrorResponse' security: - BearerAuth: [] components: schemas: RegenerateApiKeyRequest: properties: validForDays: anyOf: - type: integer maximum: 365 minimum: 1 - type: 'null' title: Validfordays description: >- New key lifetime in days (1–365). Omit to keep the account's default lifetime. examples: - 365 type: object title: RegenerateApiKeyRequest description: Request body for regenerating (rotating) a doctor account's API key. examples: - validForDays: 365 RegenerateApiKeyResponse: properties: accountId: type: string title: Accountid description: Account publicId (acc_*) the key belongs to. examples: - acc_a1b2c3d4e5f6g7h8 apiKey: type: string title: Apikey description: Raw API key. Shown only once — store it securely. examples: - id: type: string title: Id description: API key publicId (ak_*). examples: - ak_a1b2c3d4e5f6g7h8 prefix: type: string title: Prefix description: Non-secret key prefix, safe to display/store for identification. examples: - sk_prod_a1b2c3d4...e5f6 mode: type: string title: Mode examples: - prod expiresAt: anyOf: - type: string - type: 'null' title: Expiresat examples: - '2027-01-15T10:30:00Z' type: object required: - accountId - apiKey - id - prefix - mode title: RegenerateApiKeyResponse description: >- Response after rotating a doctor account's API key. Mirrors the API-key fields returned on account creation, for the rotated key. The raw key is shown only once — store it securely. examples: - accountId: acc_a1b2c3d4e5f6g7h8 apiKey: expiresAt: '2027-01-15T10:30:00Z' id: ak_a1b2c3d4e5f6g7h8 mode: prod prefix: sk_prod_a1b2c3d4...e5f6 ErrorResponse: description: Envoltorio estandarizado de respuesta de error. properties: error: $ref: '#/components/schemas/ErrorDetailWithRequestId' required: - error title: ErrorResponse type: object ErrorDetailWithRequestId: description: >- Top-level error object: :class:`ErrorDetail` plus the request correlation id. Kept as a subclass rather than a field on ``ErrorDetail`` because ``ErrorDetail`` is also the per-item error shape inside the batch account-creation response (``BatchAccountResult.error``), which is serialized with nulls included. Adding the field there would publish ``"requestId": null`` on an HTTP 200, and there is only ever one request id per batch anyway -- batch callers read the ``X-Request-ID`` response header. properties: type: description: Broad error category for high-level handling. examples: - invalid_request_error title: Type type: string code: description: Machine-readable error code. Clients should switch on this value. examples: - parameter_invalid title: Code type: string message: description: Human-readable error message ending with a period. examples: - >- idCountry must be a valid country name, ISO alpha-2, or ISO alpha-3 code. title: Message type: string param: anyOf: - type: string - type: 'null' default: null description: The request field that caused the error, if applicable. examples: - idCountry title: Param details: anyOf: - additionalProperties: true type: object - type: 'null' default: null description: Optional structured, machine-readable context for the error. examples: - pendingConsultations: - sessionId: abc123 url: https://... title: Details requestId: anyOf: - type: string - type: 'null' default: null description: >- Unique id for this request, identical to the X-Request-ID response header. Quote it when contacting support. examples: - 3f9a1c2e-5b7d-4a21-9f0c-8e6d4b2a1c30 title: Requestid required: - type - code - message title: ErrorDetailWithRequestId type: object securitySchemes: BearerAuth: type: http scheme: bearer description: Clave API enviada como token Bearer ````