Text parafrazat despre "The OpenAI API uses API keys for authentication. You can create API keys at a user or service accoun..."

Mai jos găsești 4 variante diferite de exprimare pentru același text, fiecare cu stilul său distinct.

Textul Original

The OpenAI API uses API keys for authentication. You can create API keys at a user or service account level. Service accounts are tied to a "bot" individual and should be used to provision access for production systems. Each API key can be scoped to one of the following, Project keys - Provides access to a single project (preferred option); access Project API keys by selecting the specific project you wish to generate keys against. User keys - Our legacy keys. Provides access to all organizations and all projects that user has been added to; access API Keys to view your available keys. We highly advise transitioning to project keys for best security practices, although access via this method is currently still supported. Remember that your API key is a secret! Do not share it with others or expose it in any client-side code (browsers, apps). Production requests must be routed through your own backend server where your API key can be securely loaded from an environment variable or key management service.

Generat în data de: 07 ianuarie 2025

Varianta Standard

The OpenAI API employs API keys for authentication purposes. You can generate API keys at either the user level or the service account level. Service accounts are associated with a "bot" entity and are recommended for granting access to production environments. Each API key can be assigned to one of the following categories: - Project keys: These allow access to a single project and are the preferred choice. You can obtain Project API keys by selecting the specific project for which you want to create keys. - User keys: These are our older keys that provide access to all organizations and projects that the user is part of. You can view your available API Keys to manage these. While access via user keys is still supported, we strongly recommend transitioning to project keys for enhanced security. It is important to keep your API key confidential! Avoid sharing it with others or exposing it in client-side code, such as in browsers or applications. All production requests should be routed through your own backend server, where your API key can be securely retrieved from an environment variable or a key management service.