LeadIQ User Management API Guide

Auth method: Not documented

User object field mapping is not yet verified for this app.

Endpoint coverage is not yet verified for this app.

• Rate limits: Not documented

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: Not documented

• Pagination method: none

• Default page size: 0

• Max page size: 0

• Pagination pointer: Not documented

• Webhooks available: No

• Webhook notes: No webhook documentation found in official sources.

• Alternative event strategy: SCIM provisioning via Okta is the only documented automated user lifecycle mechanism.

• SCIM available: Yes

• SCIM version: 2.0

• Plan required: Enterprise (SCIM is an add-on; SSO prerequisite at $4,800/year add-on)

• Endpoint: Not documented

• Supported operations: Create user, Deactivate user

Limitations:

• SCIM endpoint URL not publicly documented; provisioned through Okta integration setup in LeadIQ admin settings.
• SSO must be enabled before SCIM can be configured.
• Only Okta is documented as a supported IdP for SCIM.
• Entra ID, Google Workspace, and OneLogin are not documented as supported IdPs.
• Specific SCIM attribute mappings and supported schemas are not publicly published.
• SCIM is an additional cost on top of the Enterprise plan.

The only documented automation scenario is Okta SCIM provisioning under an active Enterprise plus SSO configuration.

The setup flow requires generating a SCIM bearer token and base URL from within the LeadIQ admin UI, configuring the LeadIQ Okta application with those credentials, mapping Okta user attributes to LeadIQ SCIM attributes per the Okta/LeadIQ integration guide, and assigning users or groups in Okta to trigger provisioning.

Entra ID, Google Workspace, and OneLogin are not documented as supported IdPs. Any identity graph that routes through a non-Okta IdP has no supported SCIM path into LeadIQ and would require manual provisioning as a fallback. The SCIM endpoint carries no public schema reference and is not introspectable outside the admin UI.

Provision users via Okta SCIM (Enterprise)

1. Ensure LeadIQ Enterprise plan is active with SSO add-on enabled.
2. In LeadIQ admin settings, navigate to the SSO/SCIM configuration section.
3. Generate a SCIM bearer token and copy the SCIM base URL provided by LeadIQ.
4. In Okta, add the LeadIQ application and configure SCIM provisioning using the bearer token and base URL.
5. Map Okta user attributes to LeadIQ SCIM attributes as documented in the Okta/LeadIQ integration guide.
6. Assign users or groups in Okta to trigger provisioning to LeadIQ.

Watch out for: SCIM endpoint URL and token are only accessible inside the LeadIQ admin UI; they are not retrievable via any public API. SSO must be active before SCIM setup is available.

The primary integration trap is layered gating: SCIM cannot be configured until SSO is active, and SSO is a separate $4,800/year add-on that does not come bundled with the Enterprise plan. Teams that assume SCIM is included in Enterprise pricing will hit this wall during implementation, not during procurement.

The Okta-only IdP constraint is a hard architectural limit for any identity graph built on Entra ID or a multi-IdP federation layer.

The absence of a public REST API means there is no fallback for programmatic user management outside the SCIM flow - if SCIM is unavailable or unsupported for a given IdP, the only option is the admin UI.