--- title: Mixpanel SCIM API Integration on Truto slug: mixpanelscim category: Analytics canonical: "https://truto.one/integrations/detail/mixpanelscim/" --- # Mixpanel SCIM API Integration on Truto **Category:** Analytics **Status:** Beta ## Unified APIs ### Unified User Directory API - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Mixpanel SCIM account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Mixpanel SCIM.** The Proxy API is a 1-to-1 mapping of the Mixpanel SCIM API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Automate employee offboarding across analytics tools** — If you're building an IT lifecycle management platform, your customers need to revoke Mixpanel access the moment an employee is terminated. Integrating Mixpanel SCIM via Truto lets you deactivate or delete users programmatically, closing security gaps and satisfying SOC2 audit requirements. - **Detect orphaned accounts for security posture management** — SaaS security and governance tools need to continuously reconcile active Mixpanel seats against a customer's identity provider. By pulling the full Mixpanel user directory through Truto's Unified User Directory API, your app can flag accounts that exist in Mixpanel but are terminated in the source-of-truth HR system. - **Orchestrate Day-1 onboarding for data teams** — Onboarding platforms can provision new hires into Mixpanel with the correct team and project permissions before they even log in. Offering Mixpanel SCIM as a native integration makes your product indispensable for companies with large analytics teams that churn through frequent hires. - **Optimize SaaS license spend on enterprise analytics seats** — SaaS management platforms need to identify unused Mixpanel Enterprise seats — which are expensive. By listing all provisioned users via SCIM and cross-referencing activity data, your product can recommend or automatically reclaim idle licenses, saving customers real budget. - **Enable time-bound just-in-time access to analytics dashboards** — Access request tools can provision temporary Mixpanel access when a manager approves a Slack or Teams request, then automatically revoke it after a set window. This pattern is critical for enterprises that enforce least-privilege access policies. ## What you can build - **Automated Mixpanel user provisioning on employee hire** — Trigger a SCIM user creation in Mixpanel with the correct org role and team assignment the moment an employee record is created in your platform. - **One-click orphaned account revocation** — Surface a dashboard of Mixpanel users who no longer exist in the customer's directory, with an actionable button that fires a SCIM deactivation request to immediately revoke access. - **Real-time user directory sync for compliance audits** — Periodically pull all Mixpanel SCIM users and groups into your app to generate audit-ready reports showing exactly who has access to which analytics projects. - **Group-based analytics permission management** — Let your customers manage Mixpanel team memberships from within your app, ensuring users inherit the right project-level permissions without manual admin work inside Mixpanel. - **Idle seat detection and automated license reclamation** — Cross-reference provisioned Mixpanel seats against usage signals to identify inactive users and trigger automatic de-provisioning to reclaim costly Enterprise licenses. - **Temporary access grants with auto-expiry** — Provision a user into Mixpanel with a defined TTL, then automatically deactivate their account when the access window closes — no manual follow-up required. ## FAQs ### What authentication method does Mixpanel SCIM require? Mixpanel SCIM uses a Bearer token for authentication. The token must be generated by a Mixpanel Organization Admin from within the Mixpanel admin settings. Truto securely stores and manages this token on behalf of your end users. ### Are there prerequisites for end users before the integration works? Yes. Mixpanel requires the enterprise to have claimed and verified their corporate email domain inside Mixpanel's organization settings. Additionally, SCIM access is restricted to customers on Mixpanel's Enterprise plan. Without both of these, API calls will fail. ### What SCIM operations does Mixpanel support? Mixpanel supports a subset of SCIM 2.0: creating users (POST /Users), listing and retrieving users (GET /Users), updating users including deactivation (PATCH /Users), deleting users (DELETE /Users), and managing groups (POST /Groups, PATCH /Groups, GET /Groups). Truto normalizes these into its Unified User Directory API. ### How does Truto handle pagination for Mixpanel SCIM user lists? Mixpanel's SCIM API uses cursor-based pagination for listing users and groups. Truto handles this natively — your application receives a clean, paginated response without needing to manage cursors or offsets directly. ### Can I manage project-level permissions through SCIM? SCIM allows you to assign users to Mixpanel Groups (Teams), which in turn control project-level permissions. You cannot set granular per-project access directly via SCIM, but group membership is the standard mechanism Mixpanel uses for permission inheritance. ### Is the Mixpanel SCIM integration available as a pre-built Truto connector? Mixpanel SCIM is available through Truto's Unified User Directory API. Specific tools are built on request — reach out to the Truto team to enable or customize the integration for your use case.