Create a secret
const url = 'https://example.com/api/v1/secrets';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"admin_sensitive":true,"fields":{"additionalProperty":"example"},"name":"example","owner":"example","owner_kind":"platform","secret_type":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/v1/secrets \ --header 'Content-Type: application/json' \ --data '{ "admin_sensitive": true, "fields": { "additionalProperty": "example" }, "name": "example", "owner": "example", "owner_kind": "platform", "secret_type": "example" }'Seals a secret at an owner scope. Fields are validated and encrypted against the type shape. Gated by secret:create, plus platform:create when owner_kind is platform (the install-wide tier).
Request Body required
Section titled “Request Body required ”object
A URL to the JSON Schema for this object.
Admin-only visibility; omit to use the type default. Setting true requires the admin tier
The operator field map, validated against the type shape
object
The cascade key; unique per owner
The owning entity’s name; omit for a platform secret
Which tier owns this secret
A secret_type id
Responses
Section titled “ Responses ”Created
object
A URL to the JSON Schema for this object.
When true, only the admin tier may see or reveal this secret, regardless of placement
object
Whether the field is encrypted at rest and masked here
The owning entity’s id, the canonical handle; absent for a global owner
The secret_type name
The secret_type’s uuid, the stable form of secret_type
Example
{ "$schema": "/api/v1/schemas/SecretBody.json"}default
Section titled “default ”Error
object
A URL to the JSON Schema for this object.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
Example
{ "$schema": "/api/v1/schemas/ErrorModel.json", "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}