API Reference
Didit Console
Start typing to search…

Questionnaires

Didit's Questionnaires let you design structured, dynamic forms to collect additional information from users during verification. Use our visual builder to drag and drop elements, organize content into sections, localize text for multiple languages, and route results for manual review when needed.

How it works

Our questionnaire workflow is designed for flexibility and auditability:

  1. Build in the Console (No Code)

    • Drag and drop elements to create your questionnaire.
    • Organize content into multiple sections for clarity.
    • Mark elements as required or optional.
    • Configure placeholders and helper descriptions.
    • Add choices (with optional free-text follow-up) for dropdown and single-choice.
    • Configure file/image upload limits per element.

  2. Localize Content

    • Provide translations for title, description, placeholder, and choices.
    • Define supported languages and a default_language.
    • The end-user sees content automatically in the best available language.

  3. Publish and Collect

    • Activate the questionnaire and embed it in your verification flow.
    • End-users complete the sections and submit answers.
    • File uploads (documents, images) are stored and linked to the response.

  4. Review and Decide

    • Responses are saved with a status: Approved, In Review, or Not Finished.
    • You can force all questionnaire responses to go In Review, so a person manually approves them.
    • Review answers and files in the console, then mark as Approved.

Note: Questionnaires do not produce risk warnings. Governance is achieved through required fields, validation, and review workflows.

Key capabilities

  • Visual Builder: Create and manage questionnaires with an intuitive drag-and-drop editor.
  • Sections: Group related questions; add headers and separators to guide users.
  • Translations: Localize all user-facing text; select default language; support multiple languages.
  • Validation: Mark fields required; enforce max files per upload element.
  • Choice Logic: For dropdown/single-choice, optionally require additional text per selected option.
  • Uploads: Collect documents and images with file count limits (e.g., up to 3 files).
  • Manual Review: Optionally force all responses to In Review pending human approval.
  • Activation Toggle: Enable or disable the questionnaire per application.
  • Workflow Integration: Add questionnaires to KYC or run them standalone as a Questionnaire Verification workflow.
  • APIs & Webhooks: Read structured results via API and receive updates.

Element types

You can add the following element types in the builder (selectable from the console):

  • SHORT_TEXT: Single-line free text.
  • LONG_TEXT: Multi-line free text.
  • PARAGRAPH: Read-only explanatory text block.
  • DROPDOWN: Single selection from a list of choices; supports requires_text_input per choice.
  • SINGLE_CHOICE: Radio-style single selection; supports requires_text_input per choice.
  • MULTIPLE_CHOICE: Multi-select checklist.
  • NUMBER: Numeric input.
  • IMAGE: Image upload; respects max_files.
  • FILE_UPLOAD: Document upload; respects max_files.
  • TIME: Time input.
  • EMAIL: Email input.
  • ADDRESS: Address input.
  • PHONE: Phone input.
  • COUNTRY: Country selector.
  • DATE_PICKER: Date input.
  • CONSENT: Checkbox or acknowledgement control.
  • SECTION_HEADER: Visual section header (not answerable, not required).
  • SEPARATOR: Visual divider (not answerable, not required).

Behavioral notes:

  • SECTION_HEADER and SEPARATOR are presentation-only. They ignore required/placeholder/choices/file limits.
  • For choice elements, define choices as { label, value, requires_text_input? }.
  • For upload elements, set max_files (1–5) to control how many files can be attached.

Forcing manual review

Some compliance workflows require human review of every response. From the console, you can set questionnaires to always result in In Review. A reviewer then approves or requests changes, after which the response becomes Approved.

Example use cases

  • Source of Funds: Capture income sources, amounts, and upload supporting documents (e.g., payslips, statements). Combine dropdowns, long text, and file uploads.
  • Association or Membership: Record affiliations, roles, and proof of membership; include consent elements for declarations.
  • Purpose of Relationship & Expected Account Activity: Collect intent, expected transaction volumes, countries of activity, and anticipated counterparties. Use single/multiple choice, number inputs, and paragraphs for context.

See how results are structured in the Questionnaires Report page.