Scalekit API Reference

API Reference

Complete reference for all Scalekit API endpoints

Connected Accounts APIs

• List connected accounts

  Retrieves a paginated list of connected accounts for third-party integrations. Filter by organization, user, connector type, provider, or identifier. Returns OAuth tokens, API keys, and connection status for each account. Use pagination tokens to navigate through large result sets.

  GET /api/v1/connected_accounts Connected Accounts
  • organization_id: Filter by organization ID. Returns only connected accounts associated with this organization.
  • user_id: Filter by user ID. Returns only connected accounts associated with this user.
  • connector: Filter by connector type. Connector identifier such as 'notion', 'slack', 'google', etc. Alphanumeric with hyphens and underscores allowed.
  • identifier: Filter by account identifier. The unique identifier for the connected account within the third-party service (e.g., email address, workspace ID).
  • provider: Filter by OAuth provider. The authentication provider name such as 'google', 'microsoft', 'github', etc.
  • page_size: Maximum number of connected accounts to return per page. Must be between 0 and 100. Default is typically 10.
  • page_token: Pagination token from a previous response. Use the next_page_token value from ListConnectedAccountsResponse to fetch the next page.
  • query: Text search query to filter connected accounts by name, identifier, or other searchable fields. Case-insensitive.

• Update connected account credentials

  Updates authentication credentials and configuration for an existing connected account. Modify OAuth tokens, refresh tokens, access scopes, or API configuration settings. Specify the account by ID, or by combination of organization/user, connector, and identifier. Returns the updated account with new token expiry and status information.

  PUT /api/v1/connected_accounts Connected Accounts

• Create a connected account

  Creates a new connected account with OAuth tokens or API credentials for third-party service integration. Supply authorization details including access tokens, refresh tokens, scopes, and optional API configuration. The account can be scoped to an organization or user. Returns the created account with its unique identifier and authentication status.

  POST /api/v1/connected_accounts Connected Accounts

• Get connected account details

  Retrieves complete authentication details for a connected account including OAuth tokens, refresh tokens, scopes, and API configuration. Query by account ID or by combination of organization/user, connector, and identifier. Returns sensitive credential information - use appropriate access controls.

  GET /api/v1/connected_accounts/auth Connected Accounts
  • organization_id: Organization ID for the connector
  • user_id: User ID for the connector
  • connector: Connector identifier
  • identifier: The unique identifier for the connected account within the third-party service (e.g., email address, user ID, workspace identifier).
  • id: Unique identifier for the connected account

• Generate authentication magic link

  Creates a time-limited magic link for connecting or re-authorizing a third-party account. The link directs users to the OAuth authorization flow for the specified connector. Returns the generated link URL and expiration timestamp. Links typically expire after a short duration for security.

  POST /api/v1/connected_accounts/magic_link Connected Accounts

• Delete a connected account

  Permanently removes a connected account and revokes all associated authentication credentials. Identify the account by ID, or by combination of organization/user, connector, and identifier. This action cannot be undone. All OAuth tokens and API keys for this account will be invalidated.

  POST /api/v1/connected_accounts:delete Connected Accounts

• Search connected accounts

  Search for connected accounts in your environment using a text query that matches against identifiers, providers, or connectors. The search performs case-insensitive matching across account details. Returns paginated results with account status and authentication type information.

  GET /api/v1/connected_accounts:search Connected Accounts
  • query: Search term to match against connected account identifiers, providers, or connectors. Must be at least 3 characters. Case insensitive.
  • page_size: Maximum number of connected accounts to return per page. Value must be between 1 and 30.
  • page_token: Token from a previous response for pagination. Provide this to retrieve the next page of results.
  • connection_id: Connection ID to filter connected accounts

• Execute a tool using a connected account

  Executes a tool action using authentication credentials from a connected account. Specify the tool by name and provide required parameters as JSON. The connected account can be identified by ID, or by combination of organization/user, connector, and identifier. Returns the execution result data and a unique execution ID for tracking. Use this endpoint to perform actions like sending emails, creating calendar events, or managing resources in external services.

  POST /api/v1/execute_tool Connected Accounts

Connections APIs

• List connections

  Retrieves a list of connections in the environment

  GET /api/v1/connections Connections
  • organization_id: Filter connections by organization identifier
  • domain: Filter connections by email domain associated with the organization
  • include: Filter connections by status. Use 'all' to include all connections regardless of status. Default behavior shows only active (completed and enabled) connections

• Get connection details

  Retrieves the complete configuration and status details for a specific connection by its ID within an organization. Returns all connection properties including provider settings, protocols, and current status.

  GET /api/v1/organizations/{organization_id}/connections/{id} Connections
  • organization_id: Organization identifier (required). Specifies which organization owns the connection you want to retrieve.
  • id: Connection identifier (required). Specifies which specific connection to retrieve from the organization.

• Disable organization connection

  Deactivate an existing connection for the specified organization. When disabled, users cannot authenticate using this connection. This endpoint changes the connection state from enabled to disabled without modifying other configuration settings

  PATCH /api/v1/organizations/{organization_id}/connections/{id}:disable Connections
  • organization_id: Unique identifier of the organization associated with the connection
  • id: Unique identifier for the connection to be toggled

• Enable organization connection

  Activate an existing connection for the specified organization. When enabled, users can authenticate using this connection. This endpoint changes the connection state from disabled to enabled without modifying other configuration settings

  PATCH /api/v1/organizations/{organization_id}/connections/{id}:enable Connections
  • organization_id: Unique identifier of the organization associated with the connection
  • id: Unique identifier for the connection to be toggled

Users APIs

• Resend user invitation email

  Resends an invitation email to a user who has a pending or expired invitation in the specified organization. If the invitation has expired, a new invitation will be automatically created and sent. If the invitation is still valid, a reminder email will be sent instead. Use this endpoint when a user hasn't responded to their initial invitation and you need to send them a reminder or when the original invitation has expired. The invitation email includes a secure magic link that allows the user to complete their account setup and join the organization. Each resend operation increments the resent counter.

  PATCH /api/v1/invites/organizations/{organization_id}/users/{id}/resend Users
  • organization_id: Unique identifier of the organization containing the pending invitation. Must start with 'org_' and be 1-32 characters long.
  • id: System-generated user ID of the user who has a pending invitation. Must start with 'usr_' and be 19-25 characters long.

• Add existing user to organization

  Adds an existing user to an organization and assigns them specific roles and permissions. Use this endpoint when you want to grant an existing user access to a particular organization. You can specify roles, metadata, and other membership details during the invitation process.

  POST /api/v1/memberships/organizations/{organization_id}/users/{id} Users
  • organization_id: Unique identifier of the target organization. Must start with 'org_' and be 1-32 characters long.
  • id: System-generated user ID. Must start with 'usr_' (19-25 characters)
  • external_id: External system identifier from connected directories. Must be unique across the system
  • send_invitation_email: If true, sends an activation email to the user. Defaults to true.

• Delete organization membership for user

  Removes a user from an organization by user ID or external ID. If the user has no memberships left and cascade is true, the user is also deleted. This action is irreversible and may also remove related group memberships.

  DELETE /api/v1/memberships/organizations/{organization_id}/users/{id} Users
  • organization_id: Unique organization identifier. Must start with 'org_' and be 1-32 characters long
  • id: System-generated user ID. Must start with 'usr_' (19-25 characters)
  • external_id: External system identifier from connected directories. Must match existing records

• Update organization membership for user

  Updates a user's membership details within an organization by user ID or external ID. You can update roles and membership metadata.

  PATCH /api/v1/memberships/organizations/{organization_id}/users/{id} Users
  • organization_id: Unique identifier of the organization containing the membership. Must start with 'org_' and be 1-32 characters long.
  • id: System-generated user ID. Must start with 'usr_' and be 19-25 characters long.
  • external_id: Your application's unique identifier for this user.

• List organization users

  Retrieves a paginated list of all users who are members of the specified organization. Use this endpoint to view all users with access to a particular organization, including their roles, metadata, and membership details. Supports pagination for large user lists.

  GET /api/v1/organizations/{organization_id}/users Users
  • organization_id: Unique identifier of the organization for which to list users. Must start with 'org_' and be 1-32 characters long.
  • page_size: Maximum number of users to return in a single response. Valid range: 1-100. Server may return fewer users than specified.
  • page_token: Pagination token from a previous ListUserResponse. Used to retrieve the next page of results. Leave empty for the first request.

• Create new user in organization

  Creates a new user account and immediately adds them to the specified organization. Use this endpoint when you want to create a user and grant them access to an organization in a single operation. You can provide user profile information, assign roles, and configure membership metadata. The user receives an activation email unless this feature is disabled in the organization settings.

  POST /api/v1/organizations/{organization_id}/users Users
  • organization_id:
  • send_invitation_email: If true, sends an activation email to the user. Defaults to true.

• List user permissions

  Retrieves all permissions a user has access to within a specific organization. This includes permissions from direct role assignments and inherited permissions from role hierarchy.

  GET /api/v1/organizations/{organization_id}/users/{user_id}/permissions Users
  • organization_id: Unique identifier for the organization
  • user_id: Unique identifier for the user

• List user roles

  Retrieves all roles assigned to a user within a specific organization. This includes both direct role assignments and inherited roles from role hierarchy.

  GET /api/v1/organizations/{organization_id}/users/{user_id}/roles Users
  • organization_id: Unique identifier for the organization
  • user_id: Unique identifier for the user

• List all users in environment

  Retrieves a paginated list of all users across your entire environment. Use this endpoint to view all users regardless of their organization memberships. This is useful for administrative purposes, user audits, or when you need to see all users in your Scalekit environment. Supports pagination for large user bases.

  GET /api/v1/users Users
  • page_size: Maximum number of organizations to return per page. Must be between 10 and 100
  • page_token: Pagination token from the previous response. Use to retrieve the next page of organizations

• Get support hash

  Retrieves the support email hash for the current logged in user, used for the Scalekit support system.

  GET /api/v1/users/support-hash Users

• Get user

  Retrieves all details for a user by system-generated user ID or external ID. The response includes organization memberships and user metadata.

  GET /api/v1/users/{id} Users
  • id: System-generated user ID
  • external_id: Your application's unique identifier for this organization, used to link Scalekit with your system.

• Delete user permanently

  Permanently removes a user from your environment and deletes all associated data. Use this endpoint when you need to completely remove a user account. This action deletes the user's profile, memberships, and all related data across all organizations. This operation cannot be undone, so use with caution.

  DELETE /api/v1/users/{id} Users
  • id: System-generated user ID. Must start with 'usr_' (19-25 characters)
  • external_id: External system identifier from connected directories. Must match existing records

• Update user information

  Modifies user account information including profile details, metadata, and external ID. Use this endpoint to update a user's personal information, contact details, or custom metadata. You can update the user's profile, phone number, and metadata fields. Note that fields like user ID, email address, environment ID, and creation time cannot be modified.

  PATCH /api/v1/users/{id} Users
  • id: System-generated user ID. Must start with 'usr_' and be 19-25 characters long.
  • external_id: Your application's unique identifier for this organization, used to link Scalekit with your system.

Organizations APIs

• List organizations

  Retrieve a paginated list of organizations within your environment. The response includes a `page_token` that can be used to access subsequent pages of results.

  GET /api/v1/organizations Organizations
  • page_size: Maximum number of organizations to return per page. Must be between 10 and 100
  • page_token: Pagination token from the previous response. Use to retrieve the next page of organizations
  • external_id: Your application's unique identifier for this organization, used to link Scalekit with your system

• Create an organization

  Creates a new organization in your environment. Use this endpoint to add a new tenant that can be configured with various settings and metadata

  POST /api/v1/organizations Organizations

• Get organization details

  Retrieves organization details by Scalekit ID, including name, region, metadata, and settings

  GET /api/v1/organizations/{id} Organizations
  • id: Unique scalekit-generated identifier that uniquely references an organization

• Delete an organization

  Remove an existing organization from the environment using its unique identifier

  DELETE /api/v1/organizations/{id} Organizations
  • id: Unique scalekit-generated identifier that uniquely references an organization

• Update organization details

  Updates an organization's display name, external ID, or metadata. Requires a valid organization identifier. Region code cannot be modified through this endpoint.

  PATCH /api/v1/organizations/{id} Organizations
  • id: Unique identifier of the organization to be updated

• Generate admin portal link

  Creates a single use Admin Portal URL valid for 1 minute. Once the generated admin portal URL is accessed or rendered, a temporary session of 6 hours is created to allow the admin to update SSO/SCIM configuration.

  PUT /api/v1/organizations/{id}/portal_links Organizations
  • id: Organization ID
  • features: Features to enable in the admin portal link. To enable features, append them as URL parameters: - Single Sign-On: ?features=sso - Directory Sync: ?features=dir_sync - Both features: ?features=sso&features=dir_sync Example URL: https://scalekit.com/portal/lnk_123?features=sso - dir_sync: Enables directory synchronization configuration in the portal - sso: Enables Single Sign-On (SSO) configuration in the portal

• Toggle organization settings

  Updates configuration settings for an organization. Supports modifying SSO configuration, directory synchronization settings, and session parameters. Requires organization ID and the specific settings to update.

  PATCH /api/v1/organizations/{id}/settings Organizations
  • id: Unique identifier of the organization to update settings. Must begin with 'org_' prefix

• Upsert organization user setting

  Upsert user management settings for an organization

  PATCH /api/v1/organizations/{organization_id}/settings/usermanagement Organizations
  • organization_id: ID of the organization.

Roles APIs

• List organization roles

  Retrieves all environment roles and organization specific roles. Use this endpoint to view all role definitions, including custom roles and their configurations. You can optionally include permission details for each role to understand their capabilities. This is useful for role management, auditing organization access controls, or understanding the available access levels within the organization.

  GET /api/v1/organizations/{org_id}/roles Roles
  • org_id: Unique identifier of the organization
  • include: Include additional data in the response. Valid values: 'permissions' (direct permissions only), 'permissions:all' (includes inherited permissions)

• Create organization role

  Creates a new role within the specified organization with basic configuration including name, display name, description, and permissions. Use this endpoint to define custom roles that can be assigned to users within the organization. You can create hierarchical roles by extending existing roles and assign specific permissions to control access levels. The role will be scoped to the organization and can be used for organization-specific access control.

  POST /api/v1/organizations/{org_id}/roles Roles
  • org_id: Unique identifier of the organization

• Get organization role details

  Retrieves complete information for a specific organization role including metadata, inheritance details, and optionally permissions. Use this endpoint to audit role configuration and understand the role's place in the organization's role hierarchy. You can include permission details to see what capabilities the role provides. This operation is useful for role management, user assignment decisions, or understanding organization access controls.

  GET /api/v1/organizations/{org_id}/roles/{role_name} Roles
  • org_id: Unique identifier of the organization
  • role_name: Unique name of the role
  • include: Include additional data in the response. Valid values: 'permissions' (direct permissions only), 'permissions:all' (includes inherited permissions)

• Update organization role

  Modifies an existing organization role's properties including display name, description, permissions, and inheritance settings. Use this endpoint to update role metadata, change permission assignments, or modify role hierarchy within the organization. Only the fields you specify will be updated, leaving other properties unchanged. When updating permissions, the new list replaces all existing permissions for the role.

  PUT /api/v1/organizations/{org_id}/roles/{role_name} Roles
  • org_id: Unique identifier of the organization
  • role_name: Unique name of the role

• Delete organization role

  Permanently removes a role from the organization and optionally reassigns users who had that role to a different role. Use this endpoint when you need to clean up unused roles or restructure your organization's access control system. If users are assigned to the role being deleted, you can provide a reassign_role_name to move those users to a different role before deletion. This action cannot be undone, so ensure no critical users depend on the role before deletion.

  DELETE /api/v1/organizations/{org_id}/roles/{role_name} Roles
  • org_id: Unique identifier of the organization
  • role_name: Unique name of the role
  • reassign_role_name: Role name to reassign users to when deleting this role

• Set default organization roles

  Updates the default member role for the specified organization. Use this endpoint to configure which role is automatically assigned to new users when they join the organization. The system will validate that the specified role exists and update the organization settings accordingly. This configuration affects all new user invitations and memberships within the organization.

  PATCH /api/v1/organizations/{org_id}/roles:set_defaults Roles
  • org_id: Unique identifier of the organization

• List all roles in environment

  Retrieves a comprehensive list of all roles available within the specified environment including organization roles. Use this endpoint to view all role definitions, including custom roles and their configurations. You can optionally include permission details for each role to understand their capabilities. This is useful for role management, auditing organization access controls, or understanding the available access levels within the organization.

  GET /api/v1/roles Roles
  • include: Include additional data in the response. Valid values: 'permissions' (direct permissions only), 'permissions:all' (includes inherited permissions from role hierarchy)

• Create new role in environment

  Creates a new role within the environment with specified permissions and metadata. Use this endpoint to define custom roles that can be assigned to users or groups. You can create hierarchical roles by extending existing roles, assign specific permissions, and configure display information. Roles are the foundation of your access control system and determine what actions users can perform.

  POST /api/v1/roles Roles

• Set default creator and member roles

  Updates the default creator and member roles for the current environment. Use this endpoint to configure which roles are automatically assigned to new users when they join the environment. You can specify role names for both creator and member default roles. The system will validate that the specified roles exist and update the environment settings accordingly. Returns the updated default role objects including their complete role information and permissions.

  PATCH /api/v1/roles/default Roles

• Get role details

  Retrieves complete information for a specific role including metadata and inheritance details (base role and dependent role count). Use this endpoint to audit role configuration and understand the role's place in the hierarchy. To view the role's permissions, use the ListRolePermissions endpoint.

  GET /api/v1/roles/{role_name} Roles
  • role_name: Unique name identifier of the role to retrieve. Must be alphanumeric with underscores, 1-64 characters.
  • include: Include additional data in the response. Valid values: 'permissions' (direct permissions only), 'permissions:all' (includes inherited permissions from role hierarchy)

• Update role information

  Modifies an existing role's properties including display name, description, permissions, and inheritance. Use this endpoint to update role metadata, change permission assignments, or modify role hierarchy. Only the fields you specify will be updated, leaving other properties unchanged. When updating permissions, the new list replaces all existing permissions for the role.

  PUT /api/v1/roles/{role_name} Roles
  • role_name: Unique name identifier of the role to update. Must be alphanumeric with underscores, 1-64 characters.

• Delete role and reassign users

  Permanently removes a role from the environment and reassigns users who had that role to a different role. Use this endpoint when you need to clean up unused roles or restructure your access control system. The role cannot be deleted if it has dependent roles (roles that extend it) unless you specify a replacement role. If users are assigned to the role being deleted, you must provide a reassign_role_name to move those users to a different role before deletion can proceed. This action cannot be undone, so ensure no critical users depend on the role before deletion.

  DELETE /api/v1/roles/{role_name} Roles
  • role_name: Unique name identifier of the role to delete. Must be alphanumeric with underscores, 1-64 characters.
  • reassign_role_id: Role name to reassign users to when deleting this role
  • reassign_role_name: Role name to reassign users to when deleting this role

• Delete role inheritance relationship

  Removes the base role inheritance relationship for a specified role, effectively eliminating all inherited permissions from the base role. Use this endpoint when you want to break the hierarchical relationship between roles and remove inherited permissions. The role will retain only its directly assigned permissions after this operation. This action cannot be undone, so ensure the role has sufficient direct permissions before removing inheritance. Returns no content on successful removal of the base relationship.

  DELETE /api/v1/roles/{role_name}/base Roles
  • role_name: Unique name identifier of the role whose base inheritance relationship should be removed. Must be alphanumeric with underscores, 1-64 characters.

• List dependent roles

  Retrieves all roles that directly extend the specified base role through inheritance. Use this endpoint to understand the role hierarchy and identify which roles inherit permissions from a particular base role. Provide the base role name as a path parameter, and the response will include all dependent roles with their metadata and permission information. This operation is useful for auditing role inheritance relationships, understanding the impact of changes to base roles, or managing role hierarchies effectively. Returns a list of dependent role objects including their names, display names, descriptions, and permission details.

  GET /api/v1/roles/{role_name}/dependents Roles
  • role_name: Name of the base role

• List permissions for role

  Retrieves all permissions directly assigned to the specified role, excluding permissions inherited from base roles. Use this endpoint to view the explicit permission assignments for a role, which is useful for understanding direct role capabilities, auditing permission assignments, or managing role-permission relationships. Provide the role name as a path parameter, and the response will include only the permissions that are directly assigned to that role. This operation does not include inherited permissions from role hierarchies - use ListEffectiveRolePermissions to see the complete set of permissions including inheritance. Returns a list of permission objects with their names, descriptions, and assignment metadata.

  GET /api/v1/roles/{role_name}/permissions Roles
  • role_name: Name of the role

• Add permissions to role

  Adds one or more permissions to the specified role while preserving existing permission assignments. Use this endpoint to grant additional capabilities to a role without affecting its current permission set. Provide the role name as a path parameter and a list of permission names in the request body. The system will validate that all specified permissions exist in the environment and add them to the role. Existing permission assignments remain unchanged, making this operation safe for incremental permission management. This is useful for gradually expanding role capabilities or adding new permissions as your system evolves. Returns the updated list of all permissions now assigned to the role.

  POST /api/v1/roles/{role_name}/permissions Roles
  • role_name: Name of the role

• Remove permission from role

  Removes a specific permission from the specified role, revoking that capability from all users assigned to the role. Use this endpoint to restrict role capabilities or remove unnecessary permissions. Provide both the role name and permission name as path parameters. This operation only affects the direct permission assignment and does not impact permissions inherited from base roles. If the permission is inherited through role hierarchy, you may need to modify the base role instead. This is useful for fine-tuning role permissions, implementing least-privilege access controls, or removing deprecated permissions. Returns no content on successful removal.

  DELETE /api/v1/roles/{role_name}/permissions/{permission_name} Roles
  • role_name: Name of the role
  • permission_name: Name of the permission to remove

• List effective permissions for role

  Retrieves the complete set of effective permissions for a role, including both directly assigned permissions and permissions inherited from base roles through the role hierarchy. Use this endpoint to understand the full scope of capabilities available to users assigned to a specific role. Provide the role name as a path parameter, and the response will include all permissions that apply to the role, accounting for inheritance relationships. This operation is essential for auditing role capabilities, understanding permission inheritance, or verifying the complete access scope before role assignment. Returns a comprehensive list of permission names representing the full set of effective permissions for the specified role.

  GET /api/v1/roles/{role_name}/permissions:all Roles
  • role_name: Name of the role

• Retrieve user count for role

  Retrieves the total number of users currently assigned to the specified role within the environment. Use this endpoint to monitor role usage, enforce user limits, or understand the scope of role assignments. Provide the role's unique name as a path parameter, and the response will include the current user count for that role. This operation is read-only and does not modify any data or user assignments. The count reflects all users who have the role either directly assigned or inherited through organization membership. This information is useful for capacity planning, security auditing, or understanding the impact of role changes across your user base.

  GET /api/v1/roles/{role_name}/users:count Roles
  • role_name: Unique name of the role

• Set default creator and member roles

  Updates the default creator and member roles for the current environment. Use this endpoint to configure which roles are automatically assigned to new users when they join the environment. You can specify role names for both creator and member default roles. The system will validate that the specified roles exist and update the environment settings accordingly. Returns the updated default role objects including their complete role information and permissions.

  PATCH /api/v1/roles:set_defaults Roles

API Auth APIs

• List organization API clients

  Retrieves a paginated list of API clients for a specific organization. Returns client details including metadata, scopes, and secret information (without exposing actual secret values).

  GET /api/v1/organizations/{organization_id}/clients API Auth
  • organization_id: Unique identifier of the organization whose clients to list. Must start with 'org_' prefix.
  • page_size: Maximum number of clients to return per page Maximum number of API clients to return per page. Must be between 10 and 100
  • page_token: Pagination token from the previous response Pagination token from the previous response. Use to retrieve the next page of organization clients

• Create organization API client

  Creates a new API client for an organization. Returns the client details and a plain secret (available only once).

  POST /api/v1/organizations/{organization_id}/clients API Auth
  • organization_id: Unique identifier of the organization

• Get organization API client

  Retrieves details of a specific API client in an organization.

  GET /api/v1/organizations/{organization_id}/clients/{client_id} API Auth
  • organization_id: Unique identifier of the organization
  • client_id: Unique identifier of the API client

• Delete organization API client

  Permanently deletes an API client from an organization. This operation cannot be undone and will revoke all access for the client. All associated secrets will also be invalidated. Use this endpoint to remove unused or compromised clients.

  DELETE /api/v1/organizations/{organization_id}/clients/{client_id} API Auth
  • organization_id: Unique identifier of the organization that owns the client. Must start with 'org_' prefix.
  • client_id: Unique identifier of the API client to permanently delete. Must start with 'm2morg_' prefix.

• Update organization API client

  Updates an existing organization API client. Only specified fields are modified.

  PATCH /api/v1/organizations/{organization_id}/clients/{client_id} API Auth
  • organization_id: Unique identifier of the organization
  • client_id: Unique identifier of the client

• Create organization API client secret

  Creates a new secret for an organization API client. Returns the plain secret (available only once).

  POST /api/v1/organizations/{organization_id}/clients/{client_id}/secrets API Auth
  • organization_id: Unique identifier of the organization
  • client_id: Unique identifier of the API client

• Delete organization API client secret

  Permanently deletes a secret from an organization API client. This operation cannot be undone.

  DELETE /api/v1/organizations/{organization_id}/clients/{client_id}/secrets/{secret_id} API Auth
  • organization_id: Unique identifier of the organization
  • client_id: Unique identifier of the API client
  • secret_id: Unique identifier of the client secret

Directory APIs

• List organization directories

  List organization directories

  GET /api/v1/organizations/{organization_id}/directories Directory
  • organization_id: Unique identifier of the organization

• List directory groups

  Retrieves all groups from a specified directory. Use this endpoint to view group structures from your connected identity provider.

  GET /api/v1/organizations/{organization_id}/directories/{directory_id}/groups Directory
  • organization_id: Unique identifier of the organization
  • directory_id: Unique identifier of the directory
  • page_size: Number of groups to return per page. Maximum value is 30. If not specified, defaults to 10
  • page_token: Token for pagination. Use the value returned in the 'next_page_token' field of the previous response
  • updated_after: Filter groups updated after this timestamp. Use ISO 8601 format
  • include_detail: If true, includes full group details. If false or not specified, returns basic information only
  • include_external_groups: If true, returns group and its details from external provider (default: false)

• List directory users

  Retrieves a list of all users within a specified directory for an organization. This endpoint allows you to view user accounts associated with your connected Directory Providers.

  GET /api/v1/organizations/{organization_id}/directories/{directory_id}/users Directory
  • organization_id: Unique identifier of the organization
  • directory_id: Unique identifier of the directory within the organization
  • page_size: Number of users to return per page. Maximum value is 30. If not specified, defaults to 10
  • page_token: Token for pagination. Use the value returned in the 'next_page_token' field of the previous response to retrieve the next page of results
  • include_detail: If set to true, the response will include the full user payload with all available details. If false or not specified, only essential user information will be returned
  • directory_group_id: Filter users by their membership in a specific directory group
  • updated_after: Filter users that were updated after the specified timestamp. Use ISO 8601 format

• Get directory details

  Retrieves detailed information about a specific directory within an organization

  GET /api/v1/organizations/{organization_id}/directories/{id} Directory
  • organization_id: Unique identifier of the organization
  • id: Unique identifier of the directory

• Disable a directory

  Stops synchronization of users and groups from a specified directory within an organization. This operation prevents further updates from the connected Directory provider

  PATCH /api/v1/organizations/{organization_id}/directories/{id}:disable Directory
  • organization_id: A unique identifier for the organization. The value must begin with 'org_' and be between 1 and 32 characters long
  • id: A unique identifier for a directory within the organization. The value must begin with 'dir_' and be between 1 and 32 characters long

• Enable a directory

  Activates a directory within an organization, allowing it to synchronize users and groups with the connected Directory provider

  PATCH /api/v1/organizations/{organization_id}/directories/{id}:enable Directory
  • organization_id: A unique identifier for the organization. The value must begin with 'org_' and be between 1 and 32 characters long
  • id: A unique identifier for a directory within the organization. The value must begin with 'dir_' and be between 1 and 32 characters long

Domains APIs

• List Domains

  Retrieves a paginated list of all domains configured for the specified organization. Domain types: - ALLOWED_EMAIL_DOMAIN: Trusted domains used to suggest the organization in the organization switcher during sign-in/sign-up (auth-method agnostic). - ORGANIZATION_DOMAIN: SSO discovery domains used to route users to the correct SSO provider and enforce SSO.

  GET /api/v1/organizations/{organization_id}/domains Domains
  • organization_id: Scalekit-generated unique identifier for the organization. Use either this or external_id to identify the organization.
  • include: Optional comma-separated list of additional fields to include in the response (e.g., 'verification_details').
  • page_size: Maximum number of domains to return per page. Default is 30, maximum is 100.
  • page_number: Page number to retrieve (0-based). Use 0 for the first page.
  • domain_type: The domain type. - ALLOWED_EMAIL_DOMAIN: trusted domain used to suggest the organization in the organization switcher during sign-in/sign-up. - ORGANIZATION_DOMAIN: SSO discovery domain used to route users to the correct SSO provider and enforce SSO.

• Create Domain

  Creates and associates a domain with an organization. Use one of the following domain types: - ALLOWED_EMAIL_DOMAIN: Adds a trusted email domain for organization suggestions in the organization switcher during sign-in/sign-up (auth-method agnostic). - ORGANIZATION_DOMAIN: Enables SSO domain discovery. If a user signs in with a matching email domain, Scalekit redirects them to the organization’s SSO provider and enforces SSO. The domain must be a valid business domain that you control. Public/disposable domains (e.g., gmail.com) are blocked for security.

  POST /api/v1/organizations/{organization_id}/domains Domains
  • organization_id: Scalekit-generated unique identifier for the organization. Use either this or external_id to identify the organization.

• Get Domain

  Retrieves complete details for a domain including domain type, timestamps, and configuration information.

  GET /api/v1/organizations/{organization_id}/domains/{id} Domains
  • organization_id: Scalekit-generated unique identifier for the organization. Use either this or external_id to identify the organization.
  • id: Scalekit-generated unique identifier of the domain to retrieve.

• Delete Domain

  Permanently removes a domain record from an organization. - Deleting an ORGANIZATION_DOMAIN disables SSO routing/enforcement for that domain. - Deleting an ALLOWED_EMAIL_DOMAIN stops organization suggestions for users with that email domain.

  DELETE /api/v1/organizations/{organization_id}/domains/{id} Domains
  • organization_id: Scalekit-generated unique identifier for the organization. Use either this or external_id to identify the organization.
  • id: Scalekit-generated unique identifier of the domain to be permanently deleted.

Magic link & OTP APIs

• Resend passwordless email

  Resend a verification email if the user didn't receive it or if the previous code/link has expired

  POST /api/v1/passwordless/email/resend Magic link & OTP

• Send passwordless email

  Send a verification email containing either a verification code (OTP), magic link, or both to a user's email address

  POST /api/v1/passwordless/email/send Magic link & OTP

• Verify passwordless email

  Verify a user's identity using either a verification code or magic link token

  POST /api/v1/passwordless/email/verify Magic link & OTP

Permissions APIs

• List all permissions

  Retrieves a comprehensive, paginated list of all permissions available within the environment. Use this endpoint to view all permission definitions for auditing, role management, or understanding the complete set of available access controls. The response includes pagination tokens to navigate through large sets of permissions efficiently. Each permission object contains the permission name, description, creation time, and last update time. This operation is useful for building permission selection interfaces, auditing permission usage, or understanding the scope of available access controls in your RBAC system.

  GET /api/v1/permissions Permissions
  • page_token: Page token to retrieve next page of results
  • page_size: Number of permissions to return per page (max 100)
  • type: Filter permissions by type: ALL, SCALEKIT, or ENVIRONMENT, where SCALEKIT are predefined Scalekit permissions and ENVIRONMENT are custom permissions created in the environment, default is ALL

• Create new permission

  Creates a new permission that represents a specific action users can perform within the environment. Use this endpoint to define granular access controls for your RBAC system. You can provide a unique permission name following the format 'action:resource' (for example, 'read:documents', 'write:users') and an optional description explaining the permission's purpose. The permission name must be unique across the environment and follows alphanumeric naming conventions with colons and underscores. Returns the created permission object including system-generated ID and timestamps.

  POST /api/v1/permissions Permissions

• Retrieve permission details

  Retrieves complete information for a specific permission by its unique name identifier. Use this endpoint to view permission details including description, creation time, and last update time. Provide the permission name in the path parameter following the format 'action:resource' (for example, 'read:documents'). This operation is useful for auditing permission definitions, understanding permission purposes, or verifying permission existence before assignment. Returns the complete permission object with all metadata and system-generated timestamps.

  GET /api/v1/permissions/{permission_name} Permissions
  • permission_name: Name of the permission

• Update permission details

  Modifies an existing permission's attributes including description and metadata. Use this endpoint to update permission descriptions or clarify permission purposes after creation. The permission is identified by its unique name in the path parameter, and only the fields you specify in the request body will be updated. Note that the permission name itself cannot be changed as it serves as the immutable identifier. This operation is useful for maintaining clear documentation of permission purposes or updating descriptions to reflect changes in system functionality. Returns the updated permission object with modified timestamps.

  PUT /api/v1/permissions/{permission_name} Permissions
  • permission_name: Name of the permission

• Delete permission

  Permanently removes a permission from the environment using its unique name identifier. Use this endpoint when you need to clean up unused permissions or remove access controls that are no longer relevant. The permission is identified by its name in the path parameter following the format 'action:resource'. This operation cannot be undone, so ensure no active roles depend on the permission before deletion. If the permission is currently assigned to any roles, you may need to remove those assignments first or update the roles to use alternative permissions. Returns no content on successful deletion.

  DELETE /api/v1/permissions/{permission_name} Permissions
  • permission_name: Name of the permission

Sessions APIs

• Get session details

  Retrieves comprehensive details for a specific user session including authentication status, device information, and expiration timelines. Use this endpoint to fetch current session metadata for security audits, session validation, or to display session information in user account management interfaces. Returns all session properties including the user ID, authenticated organizations, device details with browser/OS information, IP address and geolocation, and all relevant timestamps (creation, last activity, idle expiration, absolute expiration, and actual expiration if applicable).

  GET /api/v1/sessions/{session_id} Sessions
  • session_id: Unique identifier for the session. Must start with 'ses_' prefix.

• Revoke user session

  Immediately invalidates a specific user session by session ID, setting its status to 'revoked'. Once revoked, the session cannot be used for any future API requests or application access. Use this endpoint to implement session-level logout, force a user to reauthenticate on a specific device, or terminate suspicious sessions. The revocation is instantaneous and irreversible. Returns the revoked session details including the session ID, user ID, and the revocation timestamp.

  POST /api/v1/sessions/{session_id}/revoke Sessions
  • session_id: Unique identifier for the session to revoke. Must start with 'ses_' prefix.

• List user sessions

  Retrieves a paginated list of all sessions associated with a specific user across all devices and browsers. Use this endpoint to audit user activity, display all active sessions in account management interfaces, or verify user authentication status across devices. Supports filtering by session status (active, expired, revoked, logout) and time range (creation date). Returns session details for each session including device information, IP address, geolocation, and current status. The response includes pagination metadata (page tokens and total count) to handle large session lists efficiently.

  GET /api/v1/users/{user_id}/sessions Sessions
  • user_id: Unique identifier for the user whose sessions to retrieve. Must start with 'usr_' prefix.
  • page_size: Maximum number of sessions to return in a single page. Optional parameter. If not specified, defaults to a server-defined limit. Use smaller values for faster responses, larger values for fewer requests.
  • page_token: Pagination token from the previous response for retrieving the next page of results. Leave empty for the first page. Use the next_page_token from a previous response to fetch subsequent pages.
  • filter.status: Filter sessions by one or more status values. Possible values: 'active', 'expired', 'revoked', 'logout'. Leave empty to include all statuses. Multiple values use OR logic (e.g., status=['active', 'expired'] returns sessions that are either active OR expired).
  • filter.start_time: Filter to include only sessions created on or after this timestamp. Optional. Uses RFC 3339 format. Useful for querying sessions within a specific time window.
  • filter.end_time: Filter to include only sessions created on or before this timestamp. Optional. Uses RFC 3339 format. Must be after start_time if both are specified.

• Revoke all user sessions

  Immediately invalidates all active sessions for a specific user across all devices and browsers, setting their status to 'revoked'. Use this endpoint to implement global logout functionality, force re-authentication after security incidents, or terminate all sessions following a password reset or credential compromise. Only active sessions are revoked; already expired, logout, or previously revoked sessions remain unchanged. The revocation is atomic and instantaneous. Returns a list of all revoked sessions with their details and a total count of sessions revoked.

  POST /api/v1/users/{user_id}/sessions/revoke Sessions
  • user_id: Unique identifier for the user whose all sessions will be revoked. Must start with 'usr_' prefix.

Passkeys APIs

• List user's passkeys

  Retrieves all registered passkeys for the current user, including device information, creation timestamps, and display names. Use this to show users their registered authenticators.

  GET /api/v1/webauthn/credentials Passkeys
  • user_id: User ID to list credentials for (optional, current user if not provided)

• Remove a passkey

  Deletes a specific passkey credential for the current user. After removal, the authenticator can no longer be used for authentication.

  DELETE /api/v1/webauthn/credentials/{credential_id} Passkeys
  • credential_id: The credential ID to delete

• Rename a passkey

  Updates the display name of a passkey credential to help users identify their authenticators. Only the display name can be modified.

  PATCH /api/v1/webauthn/credentials/{credential_id} Passkeys
  • credential_id: The credential ID to update