Environments
Authenticate with
X-Api-Key and X-Api-Secret. Team members need team.kyc.view to read RFIs and team.kyc.submit to reply.
Webhooks
When an RFI is created or its state changes, Yativo posts to your webhook URL:rfi.created— new RFIrfi.updated— status changerfi.response_required— open and waiting on you
List RFIs
open_only=1, response_required=1
status values
Show RFI
id is Yativo’s internal RFI id (same as payload.id in webhooks). Returns one object with the same shape as a list row.
Reply to RFI
Send one complete reply per open period. Include everyrequested_items[].id in the JSON body. The same rules apply to POST /business/rfis/{id}/responses.
responses_submitted_at is set, response_required becomes false, and status moves to under_review. Further reply calls return 422 until Yativo reopens the RFI for another customer response.
requested_items[].id. Each item accepts only the field names listed in that item’s response_types.
Within a single reply, each
document_list entry must be included in that request (you can’t upload documents in a follow-up call for the same open period).
The response matches Show RFI with draft_responses populated, responses_submitted_at set, and draft_responses_at updated. Document bytes are not echoed on GET — only file_attached and description.
Returns 422 if any requested item is missing or incomplete, if the RFI is closed, or if you already replied and Yativo hasn’t reopened the RFI.

