Torii

Torii is a SaaS management platform that gives IT teams visibility into and control over the software applications used across their organization. It automates the discovery of shadow IT, centralizes an inventory of applications, licenses, and contracts, and supports governance workflows such as access reviews, spend optimization, and user lifecycle management. The Torii REST API exposes this data programmatically, letting you read and write application, contract, user, and workflow records.

Power end-to-end data operations for your Torii API with Nexla. Our bi-directional Torii connector is purpose-built for Torii, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Torii or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Torii workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Torii credential, you need an API key from your Torii account. Torii authenticates all API requests using a private API key sent as a bearer token in the Authorization header.

To obtain your Torii API key:

1. Sign in to your Torii account and navigate to Settings > API Access.

2. Click Generate API Key.

3. Select a key type. For general-purpose integrations, choose Torii API with Full access permissions (a separate Torii SCIM key type exists for SCIM-based user provisioning). Then choose an expiration date for the key.

   Torii recommends setting an expiration date on every API key for security purposes, and will send an email reminder about a month before the key expires. The expiration date cannot be changed after the key is created.

4. Click Generate to create the key, then copy the key value immediately. The full key is shown only once and cannot be retrieved again after you navigate away from the page.

5. Store the key securely, as you will need it to configure your Nexla credential.

The API key is sent as a bearer token in the Authorization header (Authorization: Bearer YOUR_API_KEY) for all requests to the Torii API. If your key is compromised or expires, generate a new one from Settings > API Access in Torii. For more information about API keys and available endpoints, see the Torii API support article and the Torii Developer Portal.

Authenticate

Credentials required

An authentication method that requires sending a unique secret token with each API request

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Torii API key in the API Key Value field. This is the key you generated in Prerequisites, sent as a bearer token in the Authorization header on every request to the Torii API.

   If your API key is compromised or expires, generate a new one from Settings > API Access in Torii and update this credential. For more information, see the Torii API support article.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Torii connector tile, then select the credential that will be used to connect to Torii, and click Next; or, create a new Torii credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Torii endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

List Apps

Retrieve a list of all applications in the Torii system.

Get Admin Audit Logs

Retrieve admin audit logs for compliance and monitoring purposes.

List Contracts

Retrieve a list of all contracts in the system.

List Roles

Retrieve all available roles in the system.

List Users

Retrieve a list of all users in the Torii system.

List App Fields

Retrieve all custom fields defined for applications.

List App Fields Metadata

Retrieve metadata information for all application fields.

Search Apps

Search for applications with optional filters and parameters.

Get App

Retrieve details for a specific application by ID.

List Contract Fields

Retrieve the list of available contract fields.

List Contract Fields Metadata

Retrieve metadata for contract fields with optional filtering.

Get Contract

Retrieve details for a specific contract by ID.

Get File Upload Parameters

Get the parameters and URL required for uploading files.

Get File Information

Retrieve metadata and information about a specific file by ID.

Get Organization

Retrieve the current organization details.

Get Parse Request

Retrieve details of a specific parse request by ID.

List User Custom Fields

List custom fields defined for users in the organization.

List User Fields Metadata

Retrieve metadata information for all user fields.

Get User

Retrieve detailed information for a specific user by ID.

Get Action Execution Logs

Retrieve logs of workflow action executions with filtering and pagination support.

Get Workflows Edit History

Retrieve the audit log of workflow edits and changes.

List Application Users

List users connected to a specific application.

Download File

Download a file by ID, typically returns binary file content.

List plugin fields

Retrieve all fields associated with a specific plugin.

List Resource Types

Retrieve all SCIM 2.0 resource types supported by the service provider.

List Schemas

Retrieve all SCIM 2.0 schemas supported by the service provider.

Get Service Provider Configuration

Retrieve the SCIM 2.0 service provider configuration and capabilities.

List Users

Retrieve a paginated list of users with optional filtering and sorting.

List user applications

Retrieve all applications assigned to a specific user with pagination support.

Get User By ID

Retrieve a specific user by their ID using SCIM 2.0 format.

Get User Application

Retrieves details of a specific application assigned to a user.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Torii data sources can also be manually configured to ingest data from any valid Torii API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Torii data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Torii destination, and select the Send to Destination option from the menu. Select the Torii connector from the list of available destination connectors, then select the credential that will be used to connect to Torii, and click Next; or, create a new Torii credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Torii endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Add App

Create a new application in the Torii system.

Create Contract

Create a new contract in the Torii system.

Create a New Field

Create a new custom field for applications.

Update App

Update properties of a specific application by ID.

Update Contract

Update properties of a specific contract by ID.

Delete Contract

Delete a specific contract by ID.

Update User

Update user information and custom fields.

Create User

Create a new user in the system using SCIM 2.0 format.

Update User (PUT)

Replace all attributes of a user with new values using SCIM 2.0 format.

Update User (PATCH)

Partially update specific user attributes using SCIM 2.0 patch operations.

Delete User

Deletes a user from the system via SCIM v2 protocol.

Update User Application

Updates a user's application assignment or configuration.

Create User Anonymization Request

Creates a request to anonymize a user's personal data.

Store File Information

Stores file metadata and information in the database.

Create Plugin

Creates a new plugin in the Torii system.

Run App Access Request Policy

Executes an application access request policy evaluation.

Create Custom App

Creates a new custom application in the catalog.

Match Apps

Matches applications based on provided criteria or identifiers.

Upload File

Uploads a file to the system with a maximum size of 3MB.

Generate Plugin API Key

Generate a new API key for a private plugin to enable programmatic access.

Trigger Workflow

Execute a workflow immediately by ID.

Update Plugin

Update and publish a new version of an existing plugin.

Delete Plugin

Permanently delete a plugin by UUID.

Update Field

Update the configuration of an application field.

Delete Field

Delete a field from an application.

Parse Automatically

Trigger automatic parsing of data using configured rules.

Parse Manually

Trigger manual parsing of data with specified parsing rules.

Sync Custom Integration

Synchronize data with a custom service integration.

Sync Gluu Integration

Synchronize data with the Gluu custom integration service.

Manual configuration

Torii destinations can also be manually configured to send data to any valid Torii API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Torii APIs typically expect JSON format for most operations. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Torii endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Torii endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.