hashicorp.com
HashiCorp exposes HCP Terraform and HCP REST APIs plus the self-hosted Vault HTTP API, authenticated respectively with an HCP Terraform API bearer token, an HCP service-principal client-credentials bearer token, and a Vault client token sent as `X-Vault-Token` or `Authorization: Bearer`.
- HCP Terraform APIdiscovered
- HCP APIdiscovered
- Vault HTTP APIdiscovered
In HCP Terraform API tokens, create a user, team, organization, or group API token from the HCP Terraform UI. HCP Terraform only shows the token once when you create it, so copy and store it securely. Use it as Authorization: Bearer <token>.
Create a service principal and key following Create a service principal. Save the client_id and client_secret, then exchange them at https://auth.idp.hashicorp.com/oauth2/token with grant type client_credentials and audience https://api.hashicorp.cloud as described in HCP API Overview. Use the returned bearer access token for API calls.
Authenticate to your Vault using one of its auth methods to obtain a client token, as described in Vault HTTP API authentication. You can also log in with the Vault CLI via `vault login`. Use the token as X-Vault-Token: <token> or Authorization: Bearer <token>.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing