RFI values

The values each enumerated field on a request for information takes.

​

status

Where the request itself is. Only the last two are endings.

​

resolution_reason

Why a request closed unsatisfied. null on any request that has not.

​

item status

Where one item is. An item has no closed states of its own — the request carries those.

​

answer_type

What an item is asking for, and therefore what a valid answer looks like. answer_spec on the item carries the rules for that type.

View the 9 answer types

Value	Description
text_short	A single line of text.
text_long	A longer free-text answer.
number	A numeric answer.
date	A date.
boolean	Yes or no.
choice	One value from a fixed set the item names.
identifier	An identifying number, such as a registration or tax identifier.
document	One or more files, uploaded to the item rather than sent as an answer value.
ubo_link	A person has to verify themselves. Mint a link for them rather than answering directly.

​

answer_spec by answer type

The item carries an answer_spec holding the rules its answer is validated against. Which keys it holds is fixed by the answer_type.

​

The two ubo_link shapes

Tell them apart by which keys are present:

​

The named formats

Used by format on a text or identifier item. A new named format is data on the item, not a change to this contract.

​

blocking type

What the request is anchored to. null when it is about the sub-client itself rather than one movement. There is no virtual-account anchor: a request never names which account is blocked.