How It Works
- You provide a source form ID — this form acts as a style template. The generated form inherits its fonts, colors, backgrounds, and component styles.
- You define the steps and components for the new form. Each step contains one or more components (inputs, dropdowns, scheduling widgets, etc.).
- The API creates the form, publishes it, and returns the form ID and URL.
The source form must belong to the same environment and must not be deleted. Component types that are not in the source form’s styles will automatically receive default styling.
Request
Body Parameters
The ID of an existing form to use as a style template. The generated form inherits all visual settings (fonts, colors, backgrounds, component styles) from this form.
Display name for the generated form.
Array of step objects (minimum 2). Each step represents a page/screen in the form.
Supported Component Types
Input Components
Single-line text input.
Multi-line text area.
Collects identity fields (name, email, company, etc.). This component has a strict schema — only the
fields array is accepted.Selection Components
Dropdown select menu. Requires at least one option.
Single or multi-select options question.
Scheduling Components
Embeds a calendar scheduling widget (supports Calendly, Cal.com, HubSpot, SavvyCal, RevenueHero, and more). Requires a calendar URL.
Navigation Components
Button to advance to the next step.
Display Components
A text header displayed at the top of a step.
A block of disclaimer or legal text.
Other Components
Additional component types are supported:EmailForm, FileUploader, GraphicOptions, PasswordInput, and more. These follow the same pattern — pass the type and relevant content fields.
Response
Whether the form was created successfully.
Example Response
200 - Success
