Secret values and credential references

Section ID: Guide/jea9vuochs#overview

Secret metadata, secret values and the integrations that reference them have different visibility and recovery requirements.

Store and reference a credential

Section ID: Guide/jea9vuochs#store-and-reference-a-credential

Use Create or update a secret for the accepted name, value and metadata fields. Keep the returned version when tracking credential changes. A connection references the secret by name; that reference does not authorize sending the credential to another destination.

Inspect and list

Section ID: Guide/jea9vuochs#inspect-and-list

Use Get a secret's metadata with name, or List secrets with zero-based page and pageSize. The current default page size is 50, with a maximum of 100. Continue through the result's pages to enumerate the project; a single page is not the complete inventory. These operations return metadata without values.

Remove a credential

Section ID: Guide/jea9vuochs#remove-a-credential

Call Delete a secret with name. If a registered custom MCP server refers to it, the current API refuses ordinary deletion and reports the known references. Change those references first, or deliberately use force: true with management authority and accept the affected integrations failing on later resolution.

Already-sent requests, external copies and provider revocation remain separate. A failed deletion can leave an incomplete result; do not infer that the old credential is intact. Deleting an already absent secret succeeds with a false deleted result, which may be omitted from the JSON response.

Document ID: Guide/jea9vuochs