Connections & status
Connections & status
List your connections
Returns every active connection your organization holds with the token’s
user — the recovery path when you did not store request_id at connect time.
Pending invitations are never listed: before consent there is no connection.
manifestVersion is pinned at consent — re-publishing a manifest never widens
a live connection; new asks require a new consent.
Per-slot status
This is the surface to drive your UI from: the connection’s effective state, the manifest’s presentation groups, and each slot with its grant status.
slotIdis the canonical address of an item — use it on every other route.kind/targetremain for display.verbssay what you may do BEYOND reading. Reading a granted item is what a connection is, so it needs no verb and an empty list is ordinary — the plain ask.filllets you list the slot’s candidates, attach one, or create a value in it;editlets you update or delete the granted document on the user’s behalf;keepmeans your organization holds a copy that survives revocation and receives later versions.statusisgrantedorpending— nothing else.pendingis deliberately indistinguishable from “the user refused” and from “the user has no such data”. Do not build UI that treats pending as “exists but not yet shared”; render it as not provided with a way to fill it in-app.subjectsis the cast — the people this manifest asks about beyond the account holder (“each child you cover”). A slot carryingsubjectasks about that role; withrepeat: truethe user answers it once per family member, in your app — see Relatives & subjects.verificationis assurance metadata about the current version of a granted item — what was checked, how strong, when. Never evidence, present on granted items only, and absent again the moment a new unverified version is written.stateis evaluated at call time against both clocks: the request’s state machine and the terms’ retention window. A connection past its retention readsexpiredand stops serving immediately.