--- title: Postman SCIM API Integration on Truto slug: postmanscim category: Application Development canonical: "https://truto.one/integrations/detail/postmanscim/" --- # Postman SCIM API Integration on Truto **Category:** Application Development **Status:** Beta ## Unified APIs ### Unified User Directory API - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Postman 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 Postman SCIM.** The Proxy API is a 1-to-1 mapping of the Postman 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 developer onboarding into Postman workspaces** — SaaS companies building IT automation or HRIS platforms can provision new engineering hires directly into Postman with the correct group memberships, eliminating manual invite workflows and ensuring developers have API workspace access from day one. - **Enforce instant offboarding from developer tools** — Security and compliance platforms can deactivate Postman accounts the moment an employee is terminated, ensuring immediate revocation of access to sensitive APIs, environments, and shared collections to meet SOC2 and HIPAA offboarding SLAs. - **Reclaim unused Postman Enterprise licenses** — SaaS management platforms can read the Postman user directory via SCIM, identify inactive developers, and trigger automated deactivation workflows — helping IT teams recover expensive Enterprise seat licenses without manual audits. - **Sync organizational structure to Postman groups** — Identity governance platforms can map department or team structures from a source of truth into Postman groups, ensuring workspace and collection access stays aligned with organizational changes without IT intervention. - **Enable self-serve developer access requests** — Internal developer portals can let engineers request access to specific Postman workspaces through group membership changes, replacing IT ticketing workflows with approval-based automation that provisions access in seconds. ## What you can build - **Zero-touch developer provisioning** — Automatically create Postman accounts and assign group memberships when new engineering hires are added to your platform, with no manual steps required from IT. - **Real-time offboarding enforcement** — Instantly deactivate a developer's Postman account when their employment status changes to terminated in your system, blocking access to all shared APIs and environments. - **Postman license usage dashboard** — Fetch the full Postman team directory and display active vs. inactive user counts alongside last-activity data from other sources to surface optimization opportunities. - **Group-based workspace access management** — Let admins create, delete, and manage Postman group memberships directly from your platform to control which developers can access specific workspaces and collections. - **Cross-platform identity reconciliation** — Periodically pull Postman's user directory and compare it against your identity provider records to detect orphaned accounts, naming mismatches, or ungoverned access. - **Bulk user lifecycle operations** — Ship a workflow builder that lets IT admins batch-provision, deactivate, or reactivate Postman users in bulk during org restructures or seasonal contractor cycles. ## FAQs ### What Postman plan is required for SCIM integration? Postman SCIM is available exclusively on the Enterprise plan. Teams on Free, Basic, or Professional plans cannot use the SCIM API. ### What user attributes can be managed through Postman SCIM? Postman SCIM supports managing given name, family name, and active status. Email updates are only permitted for Super Admins managing users on verified domains. Custom attributes are not supported. ### Can users be permanently deleted via the Postman SCIM API? No. Postman SCIM only supports deactivation (setting active to false), which blocks authentication. Hard deletion of user data is not available through the SCIM API. ### Does Postman SCIM support role assignment? No. Users provisioned via SCIM are defaulted to the Developer role. Role changes must be made within the Postman admin console. However, group membership — which controls workspace and collection access — is fully manageable via SCIM. ### What operations are supported for groups? You can create groups, delete groups, and manage group members (add/remove users). Group membership in Postman controls access to workspaces, APIs, and environments, making it the primary mechanism for access control via SCIM. ### Is the Postman SCIM integration available as a prebuilt connector on Truto? Postman SCIM is available through Truto's Unified User Directory API for user operations. Specific tools are built on request — reach out to the Truto team to get this integration enabled for your account.