Introduction

Dynamic forms are server-driven forms that enable flexible and adaptive data collection. They allow the Enterprise API Suite to evolve form requirements — such as adding new fields for regulatory compliance — without requiring you to update your application code.

What are dynamic forms?

Dynamic forms are defined by API responses rather than hardcoded in your application. They consist of two parts:

• JSON Schema: Defines the data structure and validation rules
• UI Schema: Defines the layout, controls, and conditional behavior

This approach is powered by JSON Forms, an open standard for describing forms in a platform-agnostic way.

Why dynamic forms?

Regulatory Adaptability

Forms automatically adapt to changing compliance requirements without app updates.

Progressive Disclosure

Questions are revealed based on previous answers, creating a guided experience.

Consistent Experience

Standardized form definitions ensure consistent behavior across platforms.

Future-Proof Integration

Your integration remains compliant as form requirements are updated.

How dynamic forms work

When an API response includes a dynamic form, you receive a schema and a uiSchema. Your application uses these to render the form dynamically.

Progressive disclosure

Forms support progressive disclosure — the ability to reveal additional fields based on previous answers. When you submit partial data, the API may return an updated schema and uiSchema with new questions influenced by your submission.

This creates a conversational flow where users only see relevant questions, improving the experience and data quality.

Prefilled forms

Some forms can be rendered with previously submitted data, allowing users to review and update their information. In these cases, you receive the schema and uiSchema alongside the existing data, which you can use to prefill the form.

Where you can find dynamic forms

KYC Processes

Several KYC processes use dynamic forms to collect user information. The specific fields required may vary based on the user’s country of residence.

Process	Description
Profile	Basic information such as name, birthdate, and citizenship. Requirements vary by country — for example, users in EU must also provide birthplace details.
Customer Due Diligence	Financial information and risk assessment
Tax Details	Tax residency and identification numbers
Crypto Risk Assessment	Knowledge assessment for crypto risks (GB residents only)
Self-Categorization Statement	Investor profile classification (GB residents only)

For more details on KYC processes, see the KYC Introduction.

Implementation approaches

You can implement dynamic form rendering using an official JSON Forms library or by building your own custom renderer. See Rendering for detailed guidance on both approaches.

Next steps

Schema Reference

Learn about JSON Schema types and validation.

UI Schema Reference

Explore layouts, controls, and rules.