Submit API

POST https://forms.pixelverse.tech/api/forms/{FORM_ID}/submit

Find the form ID in the Share tab. The endpoint accepts application/json, application/x-www-form-urlencoded and multipart/form-data (text parts only). Cross-origin requests are allowed, so you can post straight from a browser without a proxy.

Examples

<form action="https://forms.pixelverse.tech/api/forms/FORM_ID/submit" method="POST">
  <input name="name" placeholder="Your name" />
  <input name="email" type="email" required />
  <textarea name="message"></textarea>
  <input type="text" name="sweetidentity" tabindex="-1" autocomplete="off"
       style="position:absolute;left:-9999px;opacity:0" aria-hidden="true" />
  <button>Send</button>
</form>

Payload rules

• API forms are schema-less. Send any keys; they are stored as given and become columns in exports.
• Builder forms are validated against their fields. Keys are the field keys from the builder's Advanced tab. Unknown keys are ignored.
• The key named in Email field (default email) is treated as the sender's address for Reply-To and confirmations.
• sweetidentity is the honeypot. Leave it empty; a non-empty value marks the response as spam. It is removed from the stored data.
• _meta may hold utm_source, utm_medium, utm_campaign, utm_term, utm_content, page_url and time_to_complete. Anything else in it is dropped.
• Bodies over 100 KB are rejected. Send files as links, not uploads.

Response

{ "ok": true, "id": "4f2c1d9e-…" }

A honeypot catch also returns 200 with { "ok": true } and no id, so bots cannot tell they were filtered. Every other failure returns a JSON body with statusMessage; see Errors and status codes.

Redirect after a plain HTML post

A classic HTML form post navigates to the JSON response. To keep visitors on your site, submit with JavaScript (the fetch tab above) or point a builder form's thank-you redirect at a page of yours and use the hosted form instead.