Creating a Form

Create the form

From your workspace, click New form and give it a name. This creates the form immediately — there’s no separate “draft” vs “published” state to manage. It’s live the moment it exists, accepting submissions by default.

Create a new form dialog in the Raykoi dashboard

Add fields

Build the schema field-by-field — text, email, phone, number, select/multiselect, radio, checkbox, date/time, file, signature, rating/scale, and more. Each field has:

Required — enforced both client-side (instant feedback) and server-side (the actual gate — see Submissions)
Validation rules — length/range bounds, or a pattern for text fields
A submission key — defaults to the field’s ID, overridable if you need your integration’s field names to differ from the field’s internal ID

Whatever you build shows up as JSON if you fetch the form’s schema — this is what Get a Form’s Schema returns for a form with an email and a message field:

{
  "schema": {
    "fields": [
      { "id": "email", "type": "email", "label": "Email", "required": true },
      { "id": "message", "type": "textarea", "label": "Message", "required": false, "maxLength": 1000 }
    ]
  }
}

Configure spam protection

New forms start with honeypot and rate limiting on (always on, no configuration needed) but no CAPTCHA. Turn on CAPTCHA from the form’s Spam Protection settings if you expect real public traffic — see Cloudflare Turnstile, hCaptcha, or reCAPTCHA v3 to set one up.

Restrict origins (optional)

By default a form accepts submissions from any origin — useful while you’re testing locally or embedding on multiple sites. Add specific domains under Allowed Origins once you know exactly where the form will live, to reject submissions from anywhere else.

Access & restrictions and Spam protection panels in the form settings

Pausing submissions and restricting origins are Starter+ features — a Free-plan workspace sees these locked, as shown above.

Get your integration code

Every form has a Get Started tab with copy-paste code for every supported framework, pre-filled with that form’s actual public ID — the same content as Integrations, scoped to this one form.

Closing a form

Turn off Accepting submissions in the form’s settings (Starter plan or above) to stop new submissions without deleting the form or its existing data. A closed form returns 423 to anyone who tries to submit — see Submissions.

Deleting a form

Deletes the form and everything attached to it — submissions, uploaded files, analytics, webhook configuration — in one action. There’s no soft-delete or recovery window, so this is worth double-checking before you confirm it.

​Closing a form

​Deleting a form

Closing a form

Deleting a form