Skip to main content

​
What is a Unified API?

A unified API provides a single, standardized interface to interact with multiple third-party providers. Instead of learning each provider’s unique API format, authentication scheme, and data model, you write code once, and StackOne handles the differences. What StackOne normalizes:
  • Data models – Consistent field names and structures across providers (e.g., employees in BambooHR, Workday, and Personio all return the same schema)
  • Authentication – OAuth, API keys, and tokens are managed per-provider; you just pass an x-account-id header
  • Pagination – Cursor-based pagination works the same regardless of whether the provider uses offsets, pages, or cursors
  • Error formats – Standardized error responses with provider-specific details when available
Building AI agents? Use MCP Servers or AI Toolset SDKs instead. Same underlying data, optimized for LLM tool calling with built-in context management.

​
Benefits of the IAM API

Manage users, roles, groups, and policies through a single standardized API, regardless of the underlying identity providers.
Easily implement automated user access reviews across multiple systems, ensuring compliance with security policies and regulatory requirements.
StackOne’s unified approach eliminate the complexity of integrating with multiple IAM providers, reducing development time and maintenance costs.
Monitor user activity with comprehensive status tracking, including last login times, active status, and multi-factor authentication details.
Easily map roles to permissions and resources, providing granular control over access rights across different systems and applications.

​
Key Features

The table below shows key features of the IAM API that make identity and access management more efficient, from real-time synchronization to comprehensive user control:
FeatureDescription
Comprehensive User ManagementEasily create, update, and retrieve user profiles, including personal information, roles, and permissions.
Role, Policy, and Permission ManagementList and manage roles, assign permissions, and define access control policies for various resources.
Group ManagementOrganize users into groups, assign roles and permissions, and manage group memberships.
Resource Access ControlControl access to resources and ensure users have the appropriate permissions for their roles.

​
StackOne SDKs & OpenAPI Specification

Use our official SDKs for faster integration. Build with language-native libraries. Full list here.

OpenAPI Specification

​
Entity Model and Relationships

The following diagram illustrates the key entities within the IAM API: The following table outlines key entities within the IAM system and provides a brief description of each:
EntityDescription
UsersRepresents individuals with system access, including their personal information, username, email, status, activity timestamps, and multi-factor authentication settings.
RolesDefines sets of permissions and access levels that can be assigned to users or groups, with types such as admin, viewer, editor, etc.
GroupsOrganizes users into collections for easier management, with properties like name, description, type (team, department, organization, etc.), and hierarchical relationships.
PoliciesContains rules that define access controls, with associated permissions determining what actions can be performed.
PermissionsSpecifies the allowed actions on resources, such as read, read_write, approve, delete, etc.
ResourcesRepresents the objects that users can access, such as files, folders, projects, or other system components that are protected by permissions.