--- title: ServiceNow SCIM API Integration on Truto slug: servicenowscim category: Ticketing canonical: "https://truto.one/integrations/detail/servicenowscim/" --- # ServiceNow SCIM API Integration on Truto **Category:** Ticketing **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Users** — The User object represents a User. ## How it works 1. **Link your customer's ServiceNow 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 ServiceNow SCIM.** The Proxy API is a 1-to-1 mapping of the ServiceNow 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 - **Sync ServiceNow user directories for accurate ticket attribution** — SaaS platforms that create or assign tickets in ServiceNow need their internal user records to exactly match ServiceNow sys_user IDs. Pulling the ServiceNow directory via SCIM ensures every API call referencing an assigned_to or caller_id field resolves correctly, eliminating broken ticket workflows. - **Automate user provisioning and de-provisioning in ServiceNow** — HR, identity governance, and onboarding SaaS products need to create ServiceNow user accounts before day one and instantly deactivate them on termination. Offering native SCIM-based lifecycle management lets customers enforce zero-touch provisioning and immediate access revocation without custom scripting. - **Manage ServiceNow group memberships for dynamic access control** — Access governance and security SaaS platforms need to add or remove users from ServiceNow assignment groups to control who can view or resolve specific ticket queues. SCIM group operations provide a standardized way to grant and revoke this access programmatically. - **Enrich SaaS user profiles with ServiceNow identity data** — Analytics, compliance, and workflow automation platforms benefit from pulling department, title, and manager attributes from ServiceNow to drive routing logic, approval chains, and reporting without requiring customers to export CSVs or build custom integrations. - **Enable temporary break-glass access to privileged ServiceNow groups** — Security and access request SaaS tools need to grant time-bound elevated permissions in ServiceNow — such as adding a user to an admin group for a few hours. SCIM group membership operations make this automatable and auditable without touching the ServiceNow admin console. ## What you can build - **Real-time ServiceNow directory sync** — Continuously pull and reconcile ServiceNow user records — including name, email, active status, department, and manager — into your platform using the Unified User Directory API. - **Automated new hire account creation** — Create ServiceNow sys_user records the moment a new employee is onboarded in your platform, ensuring they can immediately access the Employee Service Center and have tickets opened on their behalf. - **Instant offboarding and access revocation** — Flip a user's active flag to false in ServiceNow via SCIM the moment they're marked as terminated, immediately cutting off access to sensitive ticket queues and IT portals. - **Dynamic group membership management** — Programmatically add or remove users from ServiceNow assignment and security groups to control ticket visibility, approval routing, and module access directly from your product. - **User-to-ticket identity mapping engine** — Build an internal mapping layer that links your SaaS user profiles to ServiceNow sys_user IDs, ensuring every ticket creation, assignment, or escalation API call references valid identities. - **Manager-based approval chain resolution** — Pull the manager attribute from ServiceNow user records to power approval workflows in your platform, mirroring the same routing logic ServiceNow uses for software and hardware requests. ## FAQs ### What authentication methods does ServiceNow SCIM support? ServiceNow SCIM endpoints typically support OAuth 2.0 and Basic Authentication. OAuth is recommended for production use. Truto handles the auth configuration so your team doesn't need to manage token refresh or instance-specific OAuth setup. ### What SCIM resources are available in ServiceNow? ServiceNow's SCIM v2.0 plugin exposes Users (sys_user) and Groups (sys_user_group) as standard SCIM resources, supporting Create, Read, Update, and Delete operations on both. ### Can we access custom or extended attributes like department, title, and manager? Yes. ServiceNow's SCIM implementation supports extended attributes mapped through its Robust Transform Engine (RTE). Common extensions include department, title, and manager — all of which are available through the user resource. ### Does Truto have pre-built tools for ServiceNow SCIM? ServiceNow SCIM tools are built on request. Truto's Unified User Directory API (Users) provides the standardized interface, and the Truto team will configure the ServiceNow SCIM-specific connector to match your requirements. ### How does Truto handle pagination and rate limits for ServiceNow SCIM? Truto manages SCIM pagination (startIndex/count) and respects ServiceNow instance-level rate limits automatically, so your application receives consistent paginated results without needing to handle retry logic or throttling. ### Why use SCIM instead of ServiceNow's Table API or SOAP endpoints? SCIM v2.0 is a standardized identity protocol, meaning the same integration pattern works across identity providers. ServiceNow's legacy SOAP APIs and Table API require instance-specific schema knowledge and custom field mapping. SCIM provides a predictable, interoperable contract for user and group operations.