> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pre.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Service API keys

> Store reusable third-party credentials and propagate updates to projects.

Use **API Keys** in [workspace Integrations](https://pre.dev/projects/integrations) for credentials your applications use, such as payment, email, storage, or database keys.

A **pre.dev API key** authenticates calls to pre.dev itself and is managed at [pre.dev/projects/key](https://pre.dev/projects/key). See [API authentication](/api-reference/authentication) for that workflow.

## Add a service credential

1. Open **Integrations → API Keys**.
2. Choose a provider or add a custom entry.
3. Enter the credential values and save.
4. Open the target project's **Env Vars** to review the values it needs.

Keys are stored encrypted. Use the configuration controls for secret values; do not rely on a guarantee that arbitrary agent output can never expose a value.

## Import several keys

Use **Import Keys** to paste configuration or upload a supported `.env`, `.txt`, or `.json` file. The importer can also extract values from an image. Review detected names and values before saving, especially for multiple environments or accounts.

## Apply and rotate

Reusable credentials can supply project environment configuration. Existing projects may need propagation after a change. When the interface reports projects with outdated values, review the affected projects and apply the update to the intended ones.

For a value specific to one application, use [Project setup → Env Vars](/coding-agent/integrations/env-vars). Verify the running application's behavior after updating a credential; some integrations also require an application restart or provider-side configuration.