Add an item to the information request
Adds one thing to fix, creating the draft round if the case has none. The target is an existing catalog entry addressed by section_key + field_key — officers cannot invent a field or a slot, and there is no item title: the label comes from the catalog and the officer’s text goes in message. An unknown target is a 400 invalid_target.
target_kind is field (a field of a fields-kind section) or document (a document GROUP of the documents section, its group key carried in field_key, e.g. {"target_kind":"document","section_key":"documents","field_key":"bank"}). The kind must match the section: a field section holds no groups and the documents section holds no fields. owner is a later phase, which is also why the per-owner government-ID group of the parties section cannot be targeted. audience defaults to merchant.
Nothing reaches the applicant until the round is sent. The one exception is adding to a round that is already with them (the case is in_remediation): that item is sent immediately, because an unsent item would leave its field locked while still counting as unanswered.
One open ask per target: a second item for a field the round already covers is a 409 target_already_requested, carrying that section.field as param. Edit the existing item’s message instead, or withdraw it first. A withdrawn item does not block a re-ask.
Authorizations
Session cookie for web dashboard authentication.
Path Parameters
Organization id.
KYB case id (the id from the list).
Body
Request body for kyb.AddInfoRequestItemRequest
AddInfoRequestItemRequest schema
"registration_number"
2000"The number does not match the registry, please re-enter it."
"registration"
merchant "merchant"
field, document "field"
Response
Created