Docs Reference
API fields
The fields an app reads to show Cards, held calls and activity in KIFF’s own words. For developers building an app on the KIFF API. Show these fields as given rather than writing your own text; the API calls a Card a mandate.
Cards
GET /v1/me/mandates?include=use lists the Cards with their limits;
GET /v1/me/mandates/{id}/statement returns one Card’s statement. Each
limit, in the current window, has:
limit,used,remaining(extra room included) andwindow_started;window_end, for a day’s limit only;quantity("sum(amount_cents)") andquantity_of: {kind, parameter};- for a summed limit,
unitandscale:20000,EUR,2reads €200.00.
When reissuing with POST /v1/me/mandates, send each grant’s
resources as it stands: leaving it out removes the limit. title is
the Card’s name (60 characters at most); PUT /v1/me/mandates/{id}/title
renames it.
draft_id names the agent draft whose
confirmation or trial issued the Card’s current terms, to group Cards by
draft; a Card last issued directly has none.
Held calls
GET /v1/me/card-exceptions and /{id} describe a held call:
summary: the tool’s title (“Refund a payment”);amount({minor, unit, scale}) andamount_text(“$45”);reason_text: why it’s held (”\(45 is over the \)40 limit for one call”);details: one line per argument;expires_at,answer_urlandowner_answer;taf_aboutandtaf_reason: the agent’s own words. Label them as the agent’s, never in place of KIFF’s text;kind:hold, orcard_unitfor calls refused because the Card has no limit in their unit. Acard_unitcan’t be approved once: change the Card or dismiss it.
Activity
In GET /v1/me/activity, each call has name, kind (done,
approved, not_done, sending, unknown, held or refused),
detail and amount_text. tool_outcome is what the tool reported;
with refused_by: "connection", nothing reached the tool. Show detail.
Allow this from now on
POST /v1/me/card-exceptions/{id}/allow-draft with {} drafts the
narrowest Card change that would have let a held call through, with
before and after for each change. Nothing changes until the owner
confirms the draft. It answers
{"none": ...} when nothing narrow fits. A confirm can also answer the
held call; see
One fingerprint for an install.