The Intake Forms API creates and manages AI-generated client intake forms used in Content Collector — the Studio workspace feature for collecting project content from clients. A partner creates a form for a client project, shares it with the client by adding their email, and the client fills out an AI-generated questionnaire. Forms live in the partner's Studio workspace and no site ID is needed for any endpoint.
An intake form gathers project information from a partner's client, for example
the client's name, their project details, and their answers to a tailored
questionnaire, so the partner can kick off work with everything they need.
It wraps a questionnaire with project context, the AI-generated background
material used to tailor it, the client the form is shared with, and the
client's form interaction state. The questionnaire is generated with AI the
first time the form is opened.
With the Intake Forms API, you can:
- Create, retrieve, update, and delete intake forms, including in bulk.
- Query and search intake forms across a partner's account, for example to
export all submitted forms to an external system or to power an AI assistant
that works with a partner's own data.
- Store AI-generated context and the source materials used to generate a form's
questionnaire.
- Share a form with one or more clients and track when it was first shared and
when it was submitted.
- Notify team members through Wix Automations when a client submits a form or
adds a note to it.
- View an intake form and manage its lifecycle in Content Collector at
https://www.wix.com/content-collector/partner/{intakeFormId}.
The API provides two ways to find intake forms in a partner's account:
- Query Intake Forms is for precise structured filtering and sorting. Use it
when you know exactly which forms you want, for example to export forms ordered
by
clientFormInteraction.submissionDate.
- Search Intake Forms matches a free-text expression against the client name
and project name, and supports filtering, sorting, and aggregations. Use it for
keyword lookup, for example to find the forms for a client a user asked about.
Both methods are scoped to the caller's account and don't require a site ID.
It's important to note the following points before starting to code:
- Forms live in the partner's Studio workspace and aren't tied to any specific
site. A site ID is not needed and is not accepted by any endpoint. A valid
intake form ID belonging to a different partner returns not found.
- All requests require an
Authorization header with a partner-scoped access
token or API key. To learn how to obtain credentials, see
Wix API Authentication.
- The questionnaire is generated with AI the first time the form is opened. The
Content Collector app generates the questionnaire and stores the resulting
context. This API stores the generated content but doesn't perform the
generation itself.
- Submission state is populated asynchronously.
clientFormInteraction.submissionDate
and clientFormInteraction.lastEditDate appear on the intake form after the client
submits and the submission is processed, so they may be empty until then.
- Deleting an intake form is permanent.
DeleteIntakeForm also deletes the
generated questionnaire behind the form. This is irreversible.
- Clients are Wix-authenticated. A client retrieves their form with
GetClientIntakeForm only if their signed-in email address is one of the
form's clientEmails.
- Partner: A Wix agency or freelancer who uses the Studio workspace and
Content Collector to manage client projects. Forms are scoped to the calling
partner and aren't tied to any specific site.
- Content Collector: The Studio workspace feature for collecting project
content from clients. It generates the AI questionnaire and hosts the
client-facing form view.
- Intake form: The entity managed by this API. It wraps a questionnaire with
project context, source materials, the clients it's shared with, and submission
state.
- Client: The partner's customer, who fills out the form. Identified by the
email addresses in
clientEmails.
- Client form interaction: The state of the client's response, reflected on
the intake form through
clientFormInteraction (for example, submissionDate).
- Context: AI-generated background text used to tailor the questionnaire,
stored on the intake form.
- Source materials: The partner-provided inputs (project description, uploaded
files, an existing questionnaire) used to generate the form.