JavaScript
Workspace Secrets
Delete a workspace secret
Remove a secret. Any adapter that still references it fails to resolve.
DELETE
JavaScript
Permanently remove a workspace secret.
Deleting a secret is not idempotent: a second delete of the same id is a
404.
Check what references it first
Nothing stops you deleting a secret that adapters still use. Any${NAME} reference to a deleted secret stops resolving, so a tool set whose header reads Bearer ${STRIPE_API_KEY} starts failing at call time once the secret is gone, or, for a synced MCP or OpenAPI set, fails its next sync with an unresolved_secrets error naming the missing ${NAME}.
So before deleting, confirm no adapter header still names the secret, or replace it. If you only need to change the value, rotate it in place instead of deleting and recreating, the ${NAME} references keep working.
Related
Update a workspace secret
Rotate instead of delete-and-recreate.
List workspace secrets
See what still exists.
Store and use secrets
How references resolve, and what breaks when one is gone.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The workspace the secret belongs to.
Example:
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
The secret to delete.
Example:
"wsecret_01HXKD2E5NQM3T9AYWCF586W5A"