Read through an authorized API-key connection
vault_invoke_readRead data through an authorized API-key/PAT connection using a GET request. API Vault controls authentication and destination hosts and injects the stored credential server-side; credentials are never returned. Use vault_invoke_write for any operation that sends data or changes provider state.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"connection_id": "<connection_id>",
"path": "<path>"
},
"name": "vault_invoke_read"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| headers | No | ||
| operation | No | api.request | |
| credential | No | For owner-bound custom APIs only. API Vault chooses Bearer by default; set this only when the provider docs require a custom header or query parameter. The stored key is still injected server-side and never returned. | |
| connection_id | Yes |