Forms and structured submissions
Caraer forms expose a public definition that your frontend can render and submit. Fields map to the configured business data, and forms support file uploads, multi-step flows, and nested forms for more involved submissions.
Why integrate
Section titled “Why integrate”You can build a branded intake experience while keeping the destination fields and business process connected to Caraer. Submissions enter the records the customer uses, so your website does not need a separate intake database followed by a manual transfer.
What you could build
Section titled “What you could build”Create an application, registration, or enquiry flow in your own frontend. Load the published form definition, render its steps, upload any files through the form’s public upload operation, and submit the collected values to Caraer.
Start integrating
Section titled “Start integrating”Follow Embed and submit a form. Use nested forms when a submission includes related entities. The Forms API documents public definitions, uploads, and submission responses.
Public form requests use the published form’s identifiers, rather than a private app token embedded in the browser. Treat the actual definition as the contract: required fields, nested values, and upload behaviour vary by form. Verify the resulting records as well as the success screen in your frontend.