Provider shortcuts
The fastest path. A shortcut sets the auth scheme and allowed hosts for a known service, so you supply only a name and value:Provider.list() returns the full current set — names, hosts, and token shape:
Custom secrets
When there’s no shortcut, define the auth yourself withauth and hosts. auth and provider are mutually exclusive — pick one.
The auth.type controls how the credential is attached to outbound requests:
type | Attaches as |
|---|---|
bearer | Authorization: Bearer <value> |
api-key | a named header — <header>: <prefix><value> |
basic | HTTP Basic, <username>:<value> |
custom | arbitrary header templates referencing {{ value }} |
Per-host auth
A single secret can authenticate differently per host — useful when one credential works across, say, a REST API and a git endpoint:hosts accepts wildcards (*.example.com), but not a whole top-level domain like *.com. A wildcard matches subdomains, not the domain itself — list both example.com and *.example.com if you need each.Rotation
Replace a secret’s value without recreating it. Bound sandboxes keep their environment variable; the new value is used on subsequent requests — no redeploy, no restart.List and delete
Next steps
Bind to a sandbox
Attach the secret to an environment variable so code in the sandbox can use it.