Generate form
POST api.weavely.ai/v1/forms/generate
Request
No authentication header is required for this endpoint.Body
string
A friendly name for the form (optional).
string
required
A natural-language description of the form to generate
e.g.
e.g.
"A simple contact form in Flemish".array[object]
Optional array of the following objects:
Response
string
The URL that opens the generated form in the Weavely editor.
Get form fields
GET api.weavely.ai/v1/forms/[formId]/fields
Request
Headers
string
required
Bearer <token>Your personal token.
Path Parameters
string
required
The unique identifier of the form.
Response
string
The form’s unique identifier.
string|null
The timestamp of the published version, or
null if the form has no published version.array
The list of fields in the form.
string
The field’s unique identifier.
string
The field’s display label.
string
The type of the field (e.g.,
text, datetime, etc.).Get form specification
GET api.weavely.ai/forms/:id/clientRetrieves the complete specification of a published form.
Request
No authentication required for this endpoint.Path Parameters
string
required
The unique identifier (UUID) of the form.
Response
string
The form’s unique identifier.
string
The form’s display name.
string
The Weavely plan tier (e.g., “pro”, “free”).
object
Form configuration including access, general, notifications, and security settings.
object
Complete form structure with all pages and elements.See Form Structure Reference below for complete specifications.
object
Complete theme configuration.See Theme Configuration Reference below for all available options.
array
Auto-generated variables for each input field in the form.Each variable includes
id (pattern: field:{elementId}), type, label, and dataType.array
Conditional logic rules configured for the form.See Logic Rules Reference below for structure.
array
Event-based triggers configured for the form.See Event Triggers Reference below for structure.
array
Calculated field values configured for the form.
object
Page metadata for SEO and social sharing (icon, title, description, openGraphImage).
object
Internationalization settings including language code and UI translations.
This endpoint returns the complete published form specification. The form must be published for this endpoint to return data — unpublished forms will return a 400 Bad Request error.
Create form
POST api.weavely.ai/v1/formsCreates a new form from a complete form specification.
Request
Headers
string
required
Bearer <token>Your personal token.
string
required
application/jsonBody
The request body is a complete form specification with the following structure:string
Display name for the form shown in the Weavely dashboard.
string
required
The UUID of the team to associate this form with.
boolean
Set to
true to publish the form immediately. Without this, the form is created as a draft and won’t be accessible at its public URL.object
required
The form structure containing all pages and elements.See Form Structure Reference below for page types, element types, and configurations.
object
required
The form’s visual theme configuration.See Theme Configuration Reference below for all available options.
object
Optional form settings.Omit
type for universal form behaviour. See Quiz Mode Reference, Score Mode Reference, Match Mode Reference, and Payment Mode Reference below for mode-specific settings. See Internationalisation Reference for supported language codes.array
Optional conditional logic rules.Each rule defines conditions and actions to execute based on field values.See Logic Rules Reference below for complete documentation.
array
Optional event-based triggers.Triggers execute actions in response to form events (e.g., form submission, page load).See Event Triggers Reference below for available triggers and actions.
array
Optional calculated field values.(Currently undocumented - reserved for future use)
object
Optional page-specific attributes.(Currently undocumented - reserved for future use)
Response
string
The unique identifier (UUID) of the created form.
string
Direct link to the published form. Only present when
publish is set to true in the request body.Format: https://forms.weavely.ai/{formId}string
Direct link to edit the form.Format:
https://forms.weavely.ai/editor/{formId}Example
Request:Update form
POST api.weavely.ai/v1/forms/:idUpdates an existing form. This is a partial update endpoint — only the fields provided in the request body will be updated. All omitted fields remain unchanged.
Request
Headers
string
required
Bearer <token>Your personal token.
string
required
application/jsonPath Parameters
string
required
The unique identifier (UUID) of the form to update.
Body
All body parameters are optional. Only include the fields you want to update. Omitted fields will remain unchanged.string
Update the form’s name.
object
Update the form structure containing pages and elements.See Form Structure Reference below for page types, element types, and configurations.
object
Update the form’s visual theme configuration.See Theme Configuration Reference below for all available options.
object
Update form settings.Omit
type for universal form behaviour. See Quiz Mode Reference, Score Mode Reference, Match Mode Reference, and Payment Mode Reference below for mode-specific settings. See Internationalisation Reference for supported language codes.array
Update conditional logic rules.Each rule defines conditions and actions to execute based on field values.See Logic Rules Reference below for complete documentation.
array
Update event-based triggers.Triggers execute actions in response to form events (e.g., form submission, page load).See Event Triggers Reference below for available triggers and actions.
array
Update calculated field values.(Currently undocumented - reserved for future use)
Response
string
The unique identifier (UUID) of the updated form.
Examples
Update only the form name:This endpoint performs a partial update. Only the top-level fields you include in the request body will be modified. All other fields remain unchanged. This allows you to update specific parts of a form without needing to send the entire form structure.
Form Structure Reference
Page Structure
A form consists of one or more pages. Each page has the following structure:Page Types
Ending Pages
Every universal form and quiz must have at least one ending page. Score and match forms use outcome pages instead (one per outcome). Ending pages and outcome pages can only contain display elements:headingparagraphimagelottieembed-htmlembed-audioembed-video
setEnding logic rule action to conditionally direct respondents to a different ending page — for example, based on a quiz score or a specific answer (see Logic Rules Reference below).
Element Types
Weavely forms support 27 element types organized into categories: Input Elements:input-text- Single-line text inputinput-number- Numeric inputinput-email- Email address input with validationinput-phone-number- Phone number inputinput-url- URL input with validationinput-time- Time pickerinput-date- Date pickertext-area- Multi-line text inputinput-file- File upload
checkbox-buttons- Multiple selection checkboxesradio-buttons- Single selection radio buttonsdropdown- Dropdown select menuimage-choice- Image-based selectioncheckbox- Single checkbox (yes/no)matrix- Grid of choices (rows × columns)ranking- Drag-and-drop ranking
star-rating- Star-based rating (customizable number of stars)scale-rating- Numeric scale ratingrange-slider- Slider with min/max values
heading- Heading textparagraph- Paragraph textimage- Image displaylottie- Lottie animation playerembed-html- Custom HTML embedembed-audio- Audio playerembed-video- Video embed
signature- Digital signature capture
Element Specifications
input-text
input-text
Single-line text input
input-number
input-number
Numeric input only
input-email
input-email
Email input with validation
input-phone-number
input-phone-number
Phone number input
input-url
input-url
URL input with validation
input-time
input-time
Time picker input
input-date
input-date
Date picker input
text-area
text-area
Multi-line text input
input-file
input-file
File upload input
dropdown
dropdown
Dropdown select menu
image-choice
image-choice
Image-based selection
checkbox
checkbox
Single checkbox (yes/no)
matrix
matrix
Grid of choices (rows × columns)
ranking
ranking
Drag-and-drop ranking
star-rating
star-rating
Star-based rating
scale-rating
scale-rating
Numeric scale rating
range-slider
range-slider
Slider with min/max values
heading
heading
Heading text
paragraph
paragraph
Paragraph text. Supports HTML markup and variable piping via
{{variable_id}} syntax.image
image
Image display
lottie
lottie
Lottie animation player
embed-html
embed-html
Custom HTML embed
embed-audio
embed-audio
Audio player
embed-video
embed-video
Video embed
signature
signature
Digital signature capture
Theme Configuration Reference
ThethemeJSON object controls all visual styling for the form. It contains the following sections: name, font, logo, colors, layout, visual, and components.
Theme Presets
Weavely includes 7 preset themes. Set via thename field — the preset provides default values for colors, fonts, and components. Any explicit values you set will override the preset defaults.
NovaRetroDawnDuskFrostEmberGlass
Font
Controls typography for body text and headings independently.Logo
Optional logo image displayed on the form.src to an image URL, or null for no logo.
Colors
Full color palette for the form. All values are hex codes.
You can provide only a subset of colors (e.g. just
primary and background) and the theme preset will fill in the rest.
Layout
Controls where the visual (image or color) appears relative to the form.Visual
The background visual — either an image or a solid color. Works together withlayout to determine how the visual is positioned.
Image visual:
variables object uses CSS-like properties and defaults to size: "cover", repeat: "no-repeat", position: "center" for both types.
Common combinations:
- Side image:
layout.type: "right"(or"left") +visual.type: "image"— displays a photo alongside the form - Background color:
layout.type: "under"+visual.type: "color"— fills the page behind the form with a solid color - Background image:
layout.type: "under"+visual.type: "image"— fills the page behind the form with an image - No visual:
layout.type: "clean"— form only, no visual element
Components
Controls form layout, input style, button style, and question weight.default— Rounded input stylingsquare— Square input styling
default— Rounded button stylingsquare— Square button styling
default— Default hover animationgrow— Grow effect on hover
Complete themeJSON Example
Quiz Mode Reference
Quiz mode turns a form into a scored assessment.Enabling Quiz Mode
Setsettings.type to "quiz" and optionally configure quiz-specific settings:
Quiz-Compatible Element Types
Only the following element types support quiz scoring:radio-buttonscheckbox-buttonsinput-textdropdown
The quiz Property
Add a quiz object to any compatible element to define its correct answer and score:
Quiz Variables
When quiz mode is active, four variables are automatically available for use in logic rules and answer piping:Score-Based Conditional Endings
Use quiz variables in logic rules to direct respondents to different ending pages based on their score:hideElement, showElement, hidePage, skipToPage, setEnding).
Showing Results to Respondents
Pipe quiz variables into paragraph labels using{{variable_id}} syntax. Element labels support HTML markup:
Score Mode Reference
Score mode turns a form into a scored assessment that routes respondents to different outcome pages based on their total score — ideal for lead qualification, assessments, and personality-style tests.Enabling Score Mode
Setsettings.type to "score" and define the outcomes:
Outcomes
Outcomes divide the total score into contiguous ranges. After submission, the respondent is shown the outcome page whose range their total score falls into.
The example above produces the ranges: up to 5 → Cold Lead, 6 to 10 → Warm Lead, 11 or more → Hot Lead.
Outcome Pages
Score forms use pages of typescore-outcome-page instead of ending-page. Define one page per outcome and reference it via the outcome’s pageId. Like ending pages, score outcome pages can only contain display elements (see Page Structure above).
Scoring Answers
Points are assigned per option by adding ascore property to options. The following element types support option scores:
radio-buttonscheckbox-buttonsdropdown
Score Variables
When score mode is active, two variables are automatically available:
Both can be used in logic rule conditions and piped into element labels using
{{variable_id}} syntax, e.g. Your score: {{score:total}}.
Match Mode Reference
Match mode turns a form into a personality-style quiz that matches respondents to one of several outcomes based on weighted answers — ideal for “Which X are you?” quizzes and product recommenders.Enabling Match Mode
Setsettings.type to "match" and define the outcomes:
Outcomes
Unlike score mode, match outcomes have no score ranges. Each answer option contributes weighted points to one or more outcomes, and the outcome with the highest accumulated total is matched.Outcome Pages
Match forms use pages of typematch-outcome-page instead of ending-page. Define one page per outcome and reference it via the outcome’s pageId. Like ending pages, match outcome pages can only contain display elements (see Page Structure above).
Weighting Answers
Add aweights object to each option, mapping outcome IDs to points. A single option can contribute to multiple outcomes:
radio-buttonscheckbox-buttonsdropdown
Match Variables
When match mode is active, one variable is automatically available:
It can be used in logic rule conditions and piped into element labels using
{{variable_id}} syntax, e.g. You are: {{match:outcome}}.
Payment Mode Reference
Payment mode turns a form into a payment collection form.Enabling Payment Mode
Setsettings.type to "payment":
Payment forms require additional setup in the Weavely dashboard (Stripe integration, pricing, etc.) before they can accept payments. The API call only flags the form as a payment form — it does not configure the payment provider.
Logic Rules Reference
Logic rules enable conditional behavior based on field values.Structure
Logical Operators
any- OR logic: trigger actions if ANY condition is trueall- AND logic: trigger actions if ALL conditions are true
Condition Operators
Universal (all field types):isEmpty- Check if field is empty/nullisNotEmpty- Check if field has a valueisEqual- Check if field equals a specific valueisNotEqual- Check if field does not equal a specific value
contains- Check if field contains a substringdoesNotContain- Check if field does not contain a substringstartsWith- Check if field starts with a stringendsWith- Check if field ends with a string
lessThan- Check if field is less than a valuelessThanOrEqual- Check if field is less than or equal to a valuegreaterThan- Check if field is greater than a valuegreaterThanOrEqual- Check if field is greater than or equal to a value
Available Actions
hideElement- Hide a specific elementshowElement- Show a specific elementhidePage- Hide a specific pageskipToPage- Navigate to a specific pagesetEnding- Set which ending page to display
Event Triggers Reference
Event triggers execute actions in response to form events.Structure
Available Triggers
formSubmitted- Triggered when form is successfully submittedformLoaded- Triggered when form initially loadsformPageShown- Triggered when a form page is displayed
Available Actions
openUrl- Redirect to a URL- Requires
data.urlfield
- Requires
restartForm- Restart the form from the beginning- No additional data required
Internationalisation Reference
Set the form’s language viasettings.i18n.language. The server automatically injects the correct system message translations (button labels, placeholders, error messages) for the chosen language.
Supported Languages
Note: German uses custom codes —
de for formal (“Sie”) and di for informal (“du”).