Get secret metadata
⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/vaults/{vault_id}/secrets/{name}Return the metadata of one secret: hint, allowed destinations and when it was last used. Use it to confirm a rotation landed without ever reading the value back.
For how this fits into a full workflow, see Vaults.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <key>: a private inference key (sk_live_...). See Authentication. |
syntic-beta | Yes, while in preview | agents-2026-11-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
vault_id | string | The vault id, starting with vlt_. |
name | string | The secret name. |
Response
200 OK, Content-Type: application/json
{
"name": "crm-token",
"hint": "…9f2a",
"allowed_destinations": [
"mcp.example.com"
],
"created_at": "2026-11-03T09:00:00Z",
"updated_at": "2026-11-05T09:00:00Z",
"last_used_at": "2026-11-05T10:00:03Z"
}| Field | Type | Description |
|---|---|---|
name | string | The secret’s name inside the vault. |
hint | string | The last four characters, for recognition. The value itself is never returned. |
allowed_destinations | array | Hosts the secret may be sent to. Empty means any host the session can reach. |
last_used_at | string or null | When a tool or MCP call last used it. |
Examples
curl -sS "https://app.syntic.ai/v1/vaults/vlt_01JC2B4D6F8H0K2M4P6R/secrets/crm-token" \
-H "Authorization: Bearer $SYNTIC_API_KEY" \
-H "syntic-beta: agents-2026-11-01"Errors
Errors use the error envelope and carry a request_id. Codes specific to this operation:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 404 | not_found_error | secret_not_found | No secret with this name in the vault. |
| 401 | authentication_error | invalid_api_key | The key is missing, unknown, revoked or expired. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Was this page helpful?