List active connections
const url = 'https://api.engram.page/connections';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.engram.page/connections \ --header 'Authorization: Bearer <token>'OAuth client families, device families, and PATs. Session-auth only.
Authorizations
Section titled “Authorizations”Responses
Section titled “ Responses ”Connections
object
CIMD metadata-document URL. Present only for clients that published one, in which case it is the client’s public identifier and the reason it can be verified despite redirecting to loopback.
The grant lineage this row is. One OAuth client can hold several grants over different vault sets, each its own row; pass this to DELETE /connections/oauth/{client_id} to revoke only this one. Null for PATs.
The user’s own name for this connection, when they set one.
The redirect this grant’s authorization code was delivered to. This, not redirect_uris, is what decides verified. Null for non-OAuth connections and for grants issued before it was recorded.
Every redirect the client registered. Informational only — a client may register several and choose one per authorization, so a vendor host appearing here proves nothing about this grant.
Vaults this connection may reach. Null means all vaults.
Positional against vault_ids. An entry is null when the vault is gone or outside the caller’s own scope.
Example
[ { "cimd_url": "https://claude.ai/.well-known/oauth-client", "kind": "oauth" }]