Organization

Workspace profile, branding, members, invites, and lead integrations for the active organization.

Workspace & branding

1. Display name

   Update the workspace display name shown in the app header.

2. Branding

   Upload logos and brand assets used across customer-facing surfaces.

   

Lead Integration Guide

Send leads into your workspace over HTTPS. Each request uses a Bearer token created here; the server signs it with the Lead API secret — you never need that secret in the browser or in partner documentation.

Security essentials

• Treat each token like a password. Anyone with it can create leads in this workspace only.
• Prefer a time-limited token unless the integration runs only on your secure servers.
• Use HTTPS. If a token leaks, generate a new one and stop using the old value.
• This is not your CRM login JWT — do not use your session token in place of a Lead API token.

How leads appear in the CRM

API-created leads use createdVia: external. In-app captures use internal. The Leads table shows an Origin column so you can filter by source.

Create an integration token

1. Choose token expiry

   Select how long the token should remain valid. Options: Does not expire (best for trusted server-side integrations), 90 days (good default for partner or form integrations), or 1 year (long-lived; plan to refresh before expiry).

   

2. Add a label (optional)

   Add a human-readable label stored in the token as sub for your server logs and audit trail.

3. Assign audience lists (optional)

   Select audience lists to embed in the token. Leads submitted with this token are added to those lists automatically — no list IDs are required in the JSON body.

4. Click Create token

   Copy the token immediately and store it securely. It will not be shown again.

API Endpoints

Both endpoints are POST and require the ingest Bearer token in the Authorization header.

Allowed field values (enumerations)

Use these exact strings in the JSON body:

Limits and protections

• Per-IP rate limits: ~120 requests / 60 s (configurable via LEAD_INGEST_RATE_MAX and LEAD_INGEST_RATE_WINDOW_MS).
• Request body limit: 1 MB.
• Bulk: at most 100 leads per request.

HTTP status codes

Members

1. View members

   See everyone with access to this workspace and their roles.

   

2. Invite member

   Send an invite email with the appropriate role.

   

3. Add manually

   Admins can create users manually when invite email is not preferred.

   

Additional workspaces

1. Add organization

   Create another organization when you need a separate pipeline and data boundary.