In progress
API
Direct HTTP access to vaults and secrets, for integrations that cannot use the CLI.
Not ready yet
The HTTP API is still being designed. Until it lands, everything OneGuard can do is available through the CLI — including from scripts and CI, where oneguard env pull with a read-only API key covers most of what an integration needs.
If you are blocked on something the CLI cannot do, tell us what you are building — it shapes what gets built first.
What this section will cover
- Authentication with API keys, and how read and write permissions apply
- Vaults and secrets: listing, creating, and fetching an encrypted payload
- Client-side decryption — what the server returns and what it never sees
- Errors, rate limits, and pagination