Push Secret to Vault
Credentials & Vault
Push Secret to Vault
Write a KV secret to your underlying vault via a registered integration. The raw values are forwarded to your vault and never stored by ScrapEngine.
POST
Push Secret to Vault
Overview
Writes a KV secret to the vault behind a registered integration. This is the only channel through which a raw username/password ever enters ScrapEngine — the payload is forwarded to your vault in the same request and not persisted on our side. For HashiCorp KV v2 (the default) the secret lands at<mount>/data/<path>; use this endpoint to seed the vault entries that your credential records reference.
Path Parameters
string
required
Integration ID (UUID) of the vault to write to.
Body
string
required
Vault KV path without the mount or
/data/ prefix. 1-200 characters. For KV v2 mounted at secret, this is stored under secret/data/<path>.string
default:"secret"
KV mount point. Defaults to
secret.object
required
Key/value pairs to store under the path. All values must be strings. This is the only channel in which the raw secret enters our system; it is forwarded to your vault and never stored by us.
object
Optional
custom_metadata (KV v2) for free-form labels — name, description, owner, etc. All values must be strings.Example Request
Response
Success Response (201)
string
The path the secret was written to (as supplied).
string
The mount point used — either what you supplied or the default (
secret).integer
KV v2 version assigned by vault. Omitted for backends that don’t version secrets.