curl -X DELETE "https://api.nevia.cloud/v1/secrets/01d4cnjqmc7d2pk9r4w6y8b0c3f" \
-H "Authorization: Bearer $TOKEN"{
"secret": {
"id": "01d4cnjqmc7d2pk9r4w6y8b0c3f",
"workspace": "01d4cnjjq40hnnh0nwmkg35nv2h",
"name": "DATABASE_PASSWORD",
"created_by": "01d4cnjmn4fbb1r5btxb5mypv62",
"updated_by": "01d4cnjmn4fbb1r5btxb5mypv62",
"created_at": "2026-09-10T12:34:56Z",
"updated_at": "2026-09-10T12:34:56Z",
"deleted_at": "2026-09-10T12:34:56Z"
},
"operations": [
"01d4cnjm89yk0r3xtv80dy0x7by"
]
}Authorization
bearerAuth Send the token in the Authorization: Bearer <token> header. See Authenticate.
In: header
Path Parameters
Secret id: 27 lowercase letters and digits.
^[A-Za-z0-9_-]{1,64}$Header Parameters
Optional retry key, kept 24 hours
1 <= length <= 255Behavior
A computer that references it cannot exec until a secret is created under the same name, which its references pick up, or the reference is detached with PATCH /v1/computers/{cmp} (env: {NAME: null}).
Deleting does not revoke the value: a process an exec started keeps it, and so does a computer restored from a checkpoint taken while one ran, since the guest resumes from memory. Revoke the credential at its source.
Response
application/jsonThe deleted secret's metadata, with deleted_at set.