The `conductorone-sdk-typescript` package provides a developer-friendly and type-safe TypeScript SDK for interacting with the ConductorOne API. Currently at version 1.1.1 (released October 2025), this SDK is regularly updated with a frequent release cadence, often driven by the Speakeasy CLI based on changes in the underlying ConductorOne API. Key differentiators include its strong TypeScript typing, ensuring compile-time safety and improved developer experience, and its full support for both CommonJS and ES Modules environments. It encapsulates the HTTP API for managing ConductorOne resources, offering structured access to various API operations such as managing app resource owners, entitlements, and automations, as evidenced by recent additions in `v1.1.1` and `v1.0.2`.
npm install conductorone-sdk-typescriptVerified import paths — ran on the pinned version, not inferred.
This example initializes the ConductorOne SDK client with authentication and then makes an API call to create a monitor for access conflicts, logging the result.
If working in a React environment, add `react` to your project dependencies: `npm install react` or `yarn add react`.
Consult the official changelog for `conductorone-sdk-typescript` and the ConductorOne API documentation for specific version migration guides before upgrading non-patch versions.
Ensure the `security` object with a valid `bearerAuth` token or `oauth` token is passed to the `ConductoroneSDKTypescript` constructor during initialization.
Install the package: `npm install conductorone-sdk-typescript`. Verify the import statement: `import { ConductoroneSDKTypescript } from "conductorone-sdk-typescript";`.Ensure the `ConductoroneSDKTypescript` class is correctly instantiated with all required `security` parameters, e.g., `new ConductoroneSDKTypescript({ security: { bearerAuth: 'YOUR_TOKEN' } })`.Verify that the `bearerAuth` or `oauth` token supplied during SDK initialization is correct, active, and has the necessary permissions for the API call.