Form Capture

Your website keeps its own form and your server forwards each submission to Buckhy. Buckhy stores the record, attempts the configured notification, and shows it in the website's Inbox. Storage, notification acceptance and confirmed delivery are different outcomes.

It runs server to server with a secret key. Nothing is added to your pages and nothing runs in the visitor's browser.

Visitor submits your form
        │
        ▼
Your server / route handler / function          (holds the secret key)
        │  POST https://api.buckhy.com/v1/capture
        ▼
Buckhy validates, sanitises and stores the record
        ├── emails the site's notify address
        └── shows the record in the console inbox

1. The browser posts to your endpoint, exactly as it does today.
2. Your endpoint forwards { form, page, fields, context? } with the site key.
3. Buckhy answers 201 { id } once the record is stored. Alerts and the console read from that stored record, so nothing is lost if an email fails.

1. Open Businesses > your website > Apps > Form Capture. Register and verify the website first if needed.
2. Complete Configure, then create the credential in Integrate for the selected environment. It is shown once.
3. Store it on your server as BUCKHY_CAPTURE_KEY and post:

await fetch("https://api.buckhy.com/v1/capture", {
  method: "POST",
  headers: { "Content-Type": "application/json", "X-Api-Key": process.env.BUCKHY_CAPTURE_KEY! },
  body: JSON.stringify({ form: "contact", page: "/contact", fields }),
});

4. Submit once and check the website's Inbox > Leads. Check notifications separately.
5. Run the app's Test checks and review Activate before relying on the integration.

Framework examples, visitor context, retries and a copy-paste AI-agent prompt: Install Form Capture.

See Keys for staged replacement and emergency revocation. Never retire the credential still used by your deployment.

Manage sites and keys

Open Businesses > your website > Apps to configure, test, activate, disable or resume Form Capture. Use API > Credentials for credential lifecycle actions. Check the environment before making changes.

Find submissions

Open Businesses > your website > Inbox > Leads:

Read a record

Open a lead to inspect its contact and submitted fields, change its review status, or assign it to a permitted teammate. Leads do not use the Support Desk reply workflow.

Export records

Use Export in the inbox to download JSON for the selected scope. Keep exported visitor data private and apply your organization's retention policy.

Send visitor context

Add a context object to the request — IP, user agent, referrer, landing page, language, time zone, screen, UTM — and alert emails gain one line such as Safari on iPhone · India · via instagram. Details and validation rules: Visitor context.