Workflow form API

Each stage on your adviser workflow board can have its own form API key. Your web developer uses that key to send new client details from a website form straight into that stage in the adviser portal — no manual data entry.

Keys are created in the portal under Workflows → stage menu → Connect website form.

Send a POST request with JSON. Use your live adviser login host (same domain you use to sign in).

POST https://login.cobaltlicenseesolutions.com.au/api/public/workflow-ingest

Include the stage form API key using either header:

Authorization: Bearer YOUR_FORM_API_KEY

— or —

X-Workflow-Form-Key: YOUR_FORM_API_KEY

The legacy header X-Workflow-Ingest-Key is still accepted.

Content-Type: application/json

{
  "name": "Jane Smith",
  "phone": "0412345678",
  "email": "jane@example.com"
}

• name (required) — full name
• phone (required)
• email (optional)

// 200 OK
{
  "ok": true,
  "clientId": "…",
  "placementId": "…",
  "workflowId": "…",
  "stageId": "…"
}

// Error
{ "ok": false, "error": "…" }

Common status codes: 401 invalid key, 409 client already on workflow, 429 rate limit.

Never put the API key in browser JavaScript. Proxy the submission through your server:

await fetch("https://login.cobaltlicenseesolutions.com.au/api/public/workflow-ingest", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    Authorization: "Bearer YOUR_FORM_API_KEY",
  },
  body: JSON.stringify({
    name: body.fullName,
    phone: body.phone,
    email: body.email || undefined,
  }),
});

• Treat the form API key like a password — store it in server env vars.
• Regenerate the key in the portal if it is ever exposed.
• Use HTTPS only.