Handle additional information and verification requests.
An RFI asks a user for information or an action needed to continue processing. This guide covers Core API inquiries; organisation onboarding is separate.
Find inquiries
List inquiries using the account ID:
GET /inquiry_request?account_id={account_id}&page=1&per_page=20
Use the account's organisation and environment API key, and follow pagination. Results can include shared person inquiries with account_id: null. Identify each inquiry by its own id.
Listen for Inquiry Events and fetch current state when the user returns.
Handle the request
| Type | Action |
|---|---|
standard | Show query and submit one response with a message, documents, or both. |
link | Show query and open the returned link. Completion is confirmed asynchronously; opening the link alone does not complete it. |
A standard response returns 201 and leaves the inquiry pending for review. Further submissions return 409. If a submission's result is uncertain, check response history before retrying; 409 alone does not confirm a saved response.
For an expired or unavailable hosted link, refresh the action. Inspect the returned status and link before prompting the user. Stop prompting for completed or cancelled inquiries.
Track the account separately
More RFIs may follow; live issuance has no fixed sequence. Completing an inquiry does not activate the account. Track account.created or account.issuance.failed and fetch the account for its current status.
Graph creates inquiries. The public APIs let you read, respond, and refresh supported actions; they do not let you create, edit, delete, cancel, or manually complete an inquiry.