How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
HashiCorp

HashiCorp Secrets API

The Secrets API from HashiCorp — 7 operation(s) for secrets.

Documentation Provider Profile APIs.io OpenAPI GitHub

HashiCorp Secrets API is one of 9 APIs that HashiCorp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Secrets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 14 operations across 7 paths. It is described by OpenAPI 3.2.0, at version 1.9.3.

14 operations 7 paths 0 schemas 3 DELETE4 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.9.3
License
Mozilla Public License 2.0
Resource Areas
1

Paths & Operations 14

Across 7 paths, the API surfaces 14 operations — 3 DELETE, 4 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Secrets 14
GET
/cubbyhole/{path}
HashiCorp Retrieve the secret at the specified location.
getCubbyholePath 2 params → 200
POST
/cubbyhole/{path}
HashiCorp Store a secret at the specified location.
postCubbyholePath 1 param → 200
DELETE
/cubbyhole/{path}
HashiCorp Deletes the secret at the specified location.
deleteCubbyholePath 1 param → 204
GET
/secret/config
HashiCorp Read the backend level settings.
getSecretConfig → 200
POST
/secret/config
HashiCorp Configure backend level settings that are applied to every key in the key-value store.
postSecretConfig body → 200
GET
/secret/data/{path}
HashiCorp Write, Patch, Read, and Delete data in the Key-Value Store.
getSecretDataPath 1 param → 200
POST
/secret/data/{path}
HashiCorp Write, Patch, Read, and Delete data in the Key-Value Store.
postSecretDataPath 1 param body → 200
DELETE
/secret/data/{path}
HashiCorp Write, Patch, Read, and Delete data in the Key-Value Store.
deleteSecretDataPath 1 param → 204
POST
/secret/delete/{path}
HashiCorp Marks one or more versions as deleted in the KV store.
postSecretDeletePath 1 param body → 200
POST
/secret/destroy/{path}
HashiCorp Permanently removes one or more versions in the KV store
postSecretDestroyPath 1 param body → 200
GET
/secret/metadata/{path}
HashiCorp Configures settings for the KV store
getSecretMetadataPath 2 params → 200
POST
/secret/metadata/{path}
HashiCorp Configures settings for the KV store
postSecretMetadataPath 1 param body → 200
DELETE
/secret/metadata/{path}
HashiCorp Configures settings for the KV store
deleteSecretMetadataPath 1 param → 204
POST
/secret/undelete/{path}
HashiCorp Undeletes one or more versions from the KV store.
postSecretUndeletePath 1 param body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hashicorp-secrets-api-openapi.yml Raw ↑

Other APIs HashiCorp publishes across the network.

HashiCorp Terraform
AE Profile APIs.io
HashiCorp Nomad
AE Profile APIs.io
HashiCorp Consul
AE Profile APIs.io
HashiCorp Boundary
AE Profile APIs.io
HashiCorp Vagrant
AE Profile APIs.io
HashiCorp Auth API
AE Profile APIs.io
HashiCorp Identity API
AE Profile APIs.io
HashiCorp System API
AE Profile APIs.io
#Secrets
← Back to H APIs
API Details
ID
hashicorp:hashicorp-secrets-api
Docs
https://developer.hashicorp.com/vault
Provider
HashiCorp
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=hashicorp-secrets-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/hashicorp-secrets-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of HashiCorp Secrets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.