Setup guide · Sheets and websites

Connect Website forms (API)

Send each form entry straight to 1Dashboard with a short request. It works from any website or form tool that can send an HTTP request. In the app this is the 1Dashboard API card.

What it brings in

  • A new lead for each request, with name, email, phone, company, source, status, value and any extra fields you send.
  • New leads are also sent on to Zoho CRM or a Google Sheets export, if you have those connected.

Before you start

  • Someone who can edit your website’s form handler, or a form tool that can send a POST request with headers.

Steps

Create an API key

  1. In 1Dashboard, open API keys (or click Connect on the 1Dashboard API card).
  2. Click Create your first key and name it after the website or form that will use it.
  3. Copy the key now. It starts with ot_ and is shown only once. We store only a hash, so we can’t show it again.

Send a lead

Send a POST request to the endpoint below, with your key in the Authorization header. The API keys page also shows a ready-made JavaScript snippet.

Endpoint
POST https://one-table-api.teaminsighter-d1e.workers.dev/api/public/leads
Example with curl
curl -X POST https://one-table-api.teaminsighter-d1e.workers.dev/api/public/leads \
  -H "Authorization: Bearer ot_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Sam Lee",
    "email": "[email protected]",
    "phone": "+61 400 000 000",
    "source": "Website form",
    "customFields": { "landing_page": "/quote" }
  }'

A successful request returns 201 with the new lead’s id: {"id":"lead_...","ok":true}

  • name is required, plus email or phone.
  • Optional: company, source, value (a number), status (new, contact, qualified, won or lost) and customFields for anything else, such as UTM tags.
  • The endpoint accepts requests from any website. If you can, send the request from your server or form handler so the key isn’t visible in your page’s source. If a key leaks, revoke it and create a new one.

How often it syncs

  • Instantly. Each request creates the lead straight away.
  • Each key can send about 60 leads a minute. Extra requests get a 429 response, so retry them a little later.

Each card on the Integrations page shows when it last synced, and flags anything that needs you.

Common problems

400 invalid_input

Every lead needs a name, plus an email or a phone number. Check the field names match the example, and that email is a valid address.

401 missing_api_key or invalid_api_key

Send the header exactly as Authorization: Bearer ot_... with the full key. A revoked key stops working at once, so create a new one if needed.

429 too many requests

More than about 60 requests a minute for one key. Wait a moment and retry.

Disconnect

  • Open API keys and revoke the key.
  • Any form using that key starts failing immediately, and this can’t be undone. Leads already received stay in 1Dashboard.

Still stuck?

Email [email protected] and tell us your workspace name and what you see on screen, and we will help you sort it out.

Other setup guides