> For the complete documentation index, see [llms.txt](/llms.txt).
> A full single-fetch corpus is available at [llms-full.txt](/llms-full.txt).
---
title: "Secrets"
description: "Store, list, and rotate the credentials your deployed workflows read at runtime, scoped to a project and environment."
last_verified: 2026-07-27
---


**Endpoints**: `GET /api/v1/secrets`, `POST /api/v1/secrets`, `GET /api/v1/secrets/:id`, `PUT /api/v1/secrets/:id`, `DELETE /api/v1/secrets/:id`
**Auth**: `X-API-KEY` or `Authorization: Bearer <token>` (required)
**Error envelope**: 4xx/5xx return `{"error": string, "message": string, "code": int, "hint"?: string}`


A **secret** is an encrypted value — an API key, database URL, or token — that a [deployment](/docs/api-reference/deployments.md) reads at runtime. Secrets are scoped to a project and, optionally, a single [environment](/docs/api-reference/environments.md).

## Next steps

* [Environments](/docs/api-reference/environments.md): scope a secret to a specific stage of your pipeline
* [Deployments](/docs/api-reference/deployments.md): the workflows that read secrets at runtime
* [Deploying](/docs/run/deploying.md): how secrets reach a running deployment