UNPKG

projectmanager-sdk

Version:

Software development kit for the ProjectManager.com API. for TypeScript

92 lines (91 loc) 5.19 kB
/** * ProjectManager API for TypeScript * * (c) ProjectManager.com, Inc. * * For the full copyright and license information, please view the LICENSE * file that was distributed with this source code. * * @author ProjectManager.com <support@projectmanager.com> * @copyright ProjectManager.com, Inc. * @link https://github.com/projectmgr/projectmanager-sdk-typescript */ import { ProjectManagerClient } from "../index.js"; import { AstroResult } from "../index.js"; import { ApiKeyDto } from "../index.js"; import { ApiKeyCreateDto } from "../index.js"; export declare class ApiKeyClient { private readonly client; /** * Internal constructor for this client library */ constructor(client: ProjectManagerClient); /** * Creates a new API key for the current user with the specified options. * * An API key is a credential that you can use to make REST v4 API calls for ProjectManager.com. When you create * a new API key, that API key is only visible in the response JSON for the `CreateApiKey` method. If you do not * preserve this information, it cannot be recreated. * * Some best practices for working with API keys: * * An API key is valid for a two year period after it is created. We encourage you to rotate your API keys * regularly according to your company's security policies. * * You should create separate API keys for each system that works with your API. If that API key is exposed * or if that program needs to be shut down, you can revoke that one key and reissue it. * * An API key is tied to the workspace that created it. A single API key can only interact with one workspace. * * @param body Options for the API key to create */ createApiKey(body: ApiKeyCreateDto): Promise<AstroResult<ApiKeyDto>>; /** * Returns a list of all API keys within the current workspace. * * An API key is a credential that you can use to make REST v4 API calls for ProjectManager.com. When you create * a new API key, that API key is only visible in the response JSON for the `CreateApiKey` method. If you do not * preserve this information, it cannot be recreated. * * Some best practices for working with API keys: * * An API key is valid for a two-year period after it is created. We encourage you to rotate your API keys * regularly according to your company's security policies. * * You should create separate API keys for each system that works with your API. If that API key is exposed * or if that program needs to be shut down, you can revoke that one key and reissue it. * * An API key is tied to the workspace that created it. A single API key can only interact with one workspace. * */ listApiKeys(): Promise<AstroResult<ApiKeyDto[]>>; /** * This API call revokes all existing API keys in given workspace. No existing keys will continue to work * after this call completes. We strongly encourage you to revoke a single API key at a time; this method * should only be used if you need to rapidly halt access to your product for automated systems. * * An API key is a credential that you can use to make REST v4 API calls for ProjectManager.com. When you create * a new API key, that API key is only visible in the response JSON for the `CreateApiKey` method. If you do not * preserve this information, it cannot be recreated. * * Some best practices for working with API keys: * * An API key is valid for a two year period after it is created. We encourage you to rotate your API keys * regularly according to your company's security policies. * * You should create separate API keys for each system that works with your API. If that API key is exposed * or if that program needs to be shut down, you can revoke that one key and reissue it. * * An API key is tied to the workspace that created it. A single API key can only interact with one workspace. * */ revokeAllApiKeys(): Promise<AstroResult<object>>; /** * Revokes a single API key in the current workspace. * * An API key is a credential that you can use to make REST v4 API calls for ProjectManager.com. When you create * a new API key, that API key is only visible in the response JSON for the `CreateApiKey` method. If you do not * preserve this information, it cannot be recreated. * * Some best practices for working with API keys: * * An API key is valid for a two year period after it is created. We encourage you to rotate your API keys * regularly according to your company's security policies. * * You should create separate API keys for each system that works with your API. If that API key is exposed * or if that program needs to be shut down, you can revoke that one key and reissue it. * * An API key is tied to the workspace that created it. A single API key can only interact with one workspace. * * @param id The unique identifier of the API key to revoke */ revokeAPIKey(id: string): Promise<AstroResult<object>>; }