Skip to content
API docs
Sign inOpen app

Concepts

Paid checks

Some form features need the plan to include them. You need the plan to turn one on, but whatever is already on stays on.

Which features

  • A phone field's verify, an email field's validate and a Telegram field's check need the plan feature verification.
  • An ai_autocomplete question needs aiFields.
  • settings.hideBadge needs hideBadge.
  • settings.partialCapture needs partialCapture.

The plan's features are in features of GET /v1/workspaces/{workspaceId}/entitlements.

Features in alpha

verification and aiFields are in alpha. A workspace whose stage doesn't see them yet gets 403 feature_unavailable instead of 403 plan_feature, and its entitlements show them as false whatever the plan. planFeatures in the entitlements shows what the plan itself includes.

Turning one on

Creating or updating a draft that turns on a check the workspace can't use answers 403 plan_feature. For a feature in alpha, it answers 403 feature_unavailable instead.

Turning a check on means switching it on for a question, by id, that didn't have it before, or adding a new ai_autocomplete question. Whatever is already on stays on, even if the plan no longer includes it.

Duplicating a form or restoring a version copies its checks as they are, whatever the plan.

On a plan without partialCapture, a new form starts with settings.partialCapture false, whether it starts blank or from an AI build.

AI builds and fixes never turn one on. Instead a phone isn't verified, an email or Telegram username isn't checked, and an AI autocomplete question becomes a short answer that asks the same thing.

On a live form

Such a check never blocks publishing. A live form skips a check its plan doesn't include and still keeps the lead. It shows the badge until the plan has hideBadge. With settings.partialCapture on, it saves only finished responses until the plan has partialCapture: no unfinished ones, no coming back to them, and no submission.abandoned events.