Clay 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: Yes

• Webhook notes: Clay supports outbound webhooks on Explorer plan and above. Webhooks fire on table row events (row created, row updated, enrichment completed), not on user/seat lifecycle events.

• Alternative event strategy: No user-lifecycle webhook events are documented. User provisioning must be handled manually via the Clay UI or through SSO/IdP (Okta, Entra ID) for Enterprise accounts.

• Webhook events: row.created, row.updated, enrichment.completed

• SCIM available: No
• SCIM version: Not documented
• Plan required: Enterprise
• Endpoint: Not documented

Limitations:

• SCIM provisioning is not publicly documented or confirmed as available even on Enterprise plan.
• Clay supports SSO via Okta and Entra ID on Enterprise, but SCIM automated provisioning support is unconfirmed in official documentation.
• User seat management is performed through the Clay workspace UI.

All three core user lifecycle operations - invite, offboard, and audit - are UI-only. Offboarding requires navigating to Settings → Team and manually removing the member; if SSO is configured, the IdP must also be deprovisioned, but session invalidation timing in Clay post-IdP revocation is unconfirmed.

Auditing workspace membership has no machine-readable output: there is no API endpoint to list members, and no documented export mechanism short of contacting Clay support. Webhooks are available on Explorer and above, but fire only on table row events (row.

created, row. updated, enrichment.

completed) - not on user or seat lifecycle events - making them unsuitable for provisioning automation.

Offboard a workspace member

1. No programmatic API exists to remove a user from a Clay workspace.
2. Navigate to Clay workspace Settings > Members.
3. Locate the member and select 'Remove from workspace' manually.
4. If SSO is configured (Okta/Entra), deprovision the user in the IdP to revoke SSO access; session invalidation timing is unconfirmed.

Watch out for: Without SCIM, deprovisioning is entirely manual. Revoking IdP SSO access does not guarantee immediate Clay session termination.

Invite a new team member

1. No API endpoint exists for programmatic user invitation.
2. Navigate to Clay workspace Settings > Members > Invite.
3. Enter the user's email address and assign a role (Admin, Member).
4. User receives an email invitation and must accept to gain access.

Watch out for: Role options and seat limits are plan-dependent. Enterprise accounts should confirm available roles with Clay support.

Audit current workspace members

1. No API endpoint exists to list workspace members programmatically.
2. Access Settings > Members in the Clay UI to view current members and roles.
3. For Enterprise audit requirements, contact Clay support to request a member export or explore IdP-side reporting via Okta/Entra.

Watch out for: No machine-readable member list is available via API. Audit workflows must rely on UI exports or IdP directory data.

The absence of a user management API creates a hard gap in any identity graph that expects Clay seat state to be queryable or event-driven. SSO availability on Enterprise does not imply SCIM; JIT provisioning behavior is unconfirmed in official docs, so automated account creation on first login cannot be assumed.

Credit consumption is plan-gated, and API access for webhooks requires Explorer or above, while CRM integrations require Pro or above - meaning integration depth is tied directly to plan tier. Teams that need Clay member state in their identity graph must treat Clay as a manually-reconciled source until SCIM support is officially confirmed and documented.