Embedding forms

Last updated: 22 May, 2026

For traditional websites and CMS integration work, embedding uses a script tag and a form container.

Requirements

The domain for the embedding website must be activated in Formcentric.
The script tag should be loaded with defer.
The form container must be a <div> .
data-fc-id must match the form ID from Formcentric.

See Client Static for the full Static documentation.

Example:


PHNjcmlwdCBzcmM9Imh0dHBzOi8vZm9ybS5mb3JtY2VudHJpYy5jb20vZm9ybS9mb3JtY2VudHJpYy5qcyIgZGVmZXI+PC9zY3JpcHQ+

React

For React, component-based integration via @formcentric/client-react should be used. The old, DOM-based SPA embedding via window.formcentric.initFormcentric() is no longer the recommended path for new React integration projects.

For details, please see Client React.

Vue

For Vue, component-based integration via @formcentric/client-vue should be used. Here too, the modern wrapper path should be preferred to the old DOM-based approach.

For details, please see Client Vue Cloud.

Angular

No component is officially supported for Angular at the moment. As a result, the best approach is to use a project-specific wrapper based on the SDK mount path.

For details and an example, see Client Angular.

SDK/module integration

For direct JavaScript or TypeScript integration projects without framework components, the SDK path is available via mount().

For details, please see Client SDK.

Local development

Formcentric cloud integration projects also require a domain stored in Formcentric in the local development environment. In practice, this typically means:

Local development via HTTPS
Development using a registered dev domain
Optional reverse proxy in front of the actual dev server

If your bundler or framework can run directly on a matching HTTPS domain, this is often all that is necessary. Otherwise, a reverse proxy is the simplest solution.

Use of Docker and Caddy

A simple approach is a local proxy with Docker and Caddy.

Example Caddyfile:


RE9NQUlOLlRMRCB7CiAgICB0bHMgaW50ZXJuYWwKICAgIHJldmVyc2VfcHJveHkgaHR0cDovL2RvY2tlci5ob3N0LmludGVybmFsOjQyMDAKICAgIGhlYWRlciB7CiAgICAgICAgQWNjZXNzLUNvbnRyb2wtQWxsb3ctT3JpZ2luICoKICAgICAgICBBY2Nlc3MtQ29udHJvbC1BbGxvdy1NZXRob2RzICJHRVQsIFBPU1QsIFBVVCwgREVMRVRFLCBPUFRJT05TIgogICAgICAgIEFjY2Vzcy1Db250cm9sLUFsbG93LUhlYWRlcnMgIk9yaWdpbiwgWC1SZXF1ZXN0ZWQtV2l0aCwgQ29udGVudC1UeXBlLCBBY2NlcHQiCiAgICB9Cn0K

Example docker-compose.yml:


c2VydmljZXM6CiAgY2FkZHk6CiAgICBpbWFnZTogY2FkZHk6Mi40LjYtYWxwaW5lCiAgICBwb3J0czoKICAgICAgLSAnODA6ODAnCiAgICAgIC0gJzQ0Mzo0NDMnCiAgICB2b2x1bWVzOgogICAgICAtIC4vQ2FkZHlmaWxlOi9ldGMvY2FkZHkvQ2FkZHlmaWxlCiAgICBleHRyYV9ob3N0czoKICAgICAgLSAnZG9ja2VyLmhvc3QuaW50ZXJuYWw6aG9zdC1nYXRld2F5Jwo=

The proxy can then be started with: docker compose up -d.

Your application should then be accessible at https://DOMAIN.TLD.

Next, you need to add a corresponding host entry in /etc/hosts so that the desired dev domain points to your local machine.

Example:


MTI3LjAuMC4xIERPTUFJTi5UTEQ=

After that, the domain must be approved in your Formcentric Cloud admin account. Please refer to the article Managing domains for further details.

Only after this step can the proxy be started with: docker compose up -d. Your application should then be available at https://DOMAIN.TLD . DOMAIN.TLD is a placeholder for your chosen development domain.

Bundler and framework proxy configuration

Many bundlers and frameworks offer direct support for a proxy or host configuration:

The actual technology used here is less important than the target condition:

The dev server must be reachable at a registered domain
HTTPS should be working properly
Asset and runtime URLs must match the selected host

Troubleshooting

Common sources of errors include:

Wrong embedId
Form is not yet published
Domain is not activated in Formcentric
Wrong srcUrl, dataUrl, formappUrl or designUrl
Runtime, theme or templates are not loaded
defer missing for Static
For SPA or SDK integration projects, a re-init is expected without re-mounting
Local development is not running under a matching domain/is running without HTTPS