Overview
To incorporate Torq vendor steps in your workflows or use the Torq API, you must first create a Torq integration instance or generate a bearer token. This process requires API key credentials: a client ID and a client secret. This guide walks you through creating a Torq API key.
Torq offers two levels of API keys:
Workspace API keys: Valid only in the workspace where they were created. Use these for a single workspace.
Org API keys: Created in Org administration. Use these to manage keys centrally or to span multiple workspaces.
The key name and type cannot be modified after creation.
Workspace API keys
API keys created in a workspace are specific to that workspace. Use the key created in the same workspace where you intend to run your requests.
Create a personal access key
Open API keys: Go to Workspace Settings > Security > API Keys.
Create a key: Click Create.
Enter a meaningful key name in Name.
Select a predefined expiration date, or choose a specific date by clicking Select from calendar.
Set Type to Personal access.
Click Create.
Save the credentials: Copy and securely store the client ID and secret. The secret will not be displayed again.
(Optional) Use the key: To use the key within a workspace, create a Torq Steps integration.
Users own the personal access keys they create. Removing a user from the workspace also deletes their personal access keys. Any integration or workflow step relying on that key will start failing. If the key needs to keep working regardless of who is on the team, use a service account key instead.
Create a workspace service key
Service account keys perform the same operations as a user with a similar role who has a personal access key. They are more secure and efficient because they are not associated with any individual user. Service account keys can also be created in a workflow with the Create a Service API Key step.
Open API keys: Go to Workspace Settings > Security > API Keys.
Create a key: Click Create.
Enter a meaningful key name in Name.
Select a predefined expiration date, or choose a specific date by clicking Select from calendar.
Set Type to Service account. The Role field appears.
Select a role. The role determines the key’s access level.
Click Create.
Save the credentials: Copy and securely store the client ID and secret. The secret will not be displayed again.
(Optional) Use the key: To use the service account key within a workspace, create a Torq Steps integration.
To create a key that spans workspaces, use Org API keys.
Org API keys
Org API keys are created in Org Administration. Service account keys created there can be valid in every workspace or only in specific workspaces. Selecting a scope is available to org admins only.
Create an org personal access key
Open Org Administration: Click your profile avatar and select Org Administration.
Open API keys: Go to Security > API keys.
Create a key: Click Create.
Enter a meaningful key name in Name.
Select a predefined expiration date, or choose a specific date by clicking Select from calendar.
Set Type to Personal access.
Click Create.
Save the credentials: Copy and securely store the client ID and secret. The secret will not be displayed again.
Personal access keys have no role, scope, or sharing options.
Create an org service key
Open API keys: Go to Org Administration > Security > API keys.
Create a key: Click Create.
Enter a meaningful key name in Name.
Select a predefined expiration date, or choose a specific date by clicking Select from calendar.
Set Type to Service account. The Role, Scope, and sharing options appear.
Select a role, Organization Manager or Organization Viewer.
Expand Scope and choose the workspaces the key can access.
All workspaces: Valid in every workspace in the organization, including workspaces added later. The key gains access to new workspaces automatically, without re-issuance.
Selected workspaces: Valid in specific workspaces only. Search for and select the workspaces the key can access.
(Optional) Select Allow this service account to share resources between workspaces in the organization. See Share an org service key.
Click Create.
Save the credentials: Copy and securely store the client ID and secret. The secret will not be displayed again.
(Optional) Use the key: To use the key within a workspace, create a Torq Steps integration.
The Scope column in the table shows Org-wide or the names of the workspaces the key can access.
Share an org service key
Organization Managers can manage an allowlist of service API keys that may be automatically shared across workspaces within the same organization, without manual approval. They can choose whether a specific key is eligible for automatic sharing.
Select Allow this service account to share resources between workspaces in the organization when creating a service account key in Org administration. Authorized workspaces can then access the key without manual approval.
Enabling auto-sharing does not mandate automatic acceptance. Users can still opt to keep the standard approval flow. This functionality applies only to organization-level service API keys. Workspace-level keys remain unaffected.
Audit logging
To maintain accountability for all key-sharing events, every auto-sharing action generates an audit log entry in the source workspace, including:
The shared service API key.
The user who changed the sharing settings.
The sharing scope, if defined.
Manage API keys
These steps apply to workspace and org keys. Open the API keys page for the relevant level first: Workspace Settings > Security > API Keys for workspace keys, or Org Administration > Security > API keys for org keys.
Edit an API key
A key’s name and type cannot be changed after creation. Only its expiration date can be modified.
New API keys require an expiration date at creation. Keys generated without one remain valid, and their expiration date is listed as Never. You can configure it later from the API keys page or with the Set API Key Expiration workflow step.
Open API keys: Open the API keys page for the relevant level.
Edit the key: Locate the key, click the three-dot (...) menu, and select Edit.
Select a new date: Select an Expiration date and click Save.
Expired API keys are not automatically deleted. They are marked as Expired on the API keys page and must be replaced because they are no longer valid.
Replace Torq integration API keys
Create a new key: Generate a new personal or service key, and save the credentials in a safe location.
If replacing a personal key with a service API key, assign the new key a role matching the existing key’s permissions.
Open the integration: Go to Build > Integrations > Steps > Torq, choose the integration instance to replace, and click Edit in the side menu.
Edit the integration: Paste the new client ID and client secret, and click Save.
Any workflows and steps that use this integration will use the new key.
The API key can be replaced, but the integration instance’s name cannot be modified after creation.
Use API keys in Torq
Create Torq integration instances: Create a Torq integration to authenticate steps.
Go to Build > Integrations > Steps > Torq and click Add Instance.
Give the integration instance a meaningful and unique name. Include the name of the person whose account was used to create the key.
Paste the client ID and client secret you saved earlier.
Click Add.
Create bearer tokens: The Torq API uses bearer tokens to authenticate requests.
Bearer tokens are valid for one hour (3,600 seconds).







