circle-info
Squadcast is now SolarWinds Incident Response

Overview

Squadcast SDK for TypeScript

Developer-friendly & type-safe Typescript SDK specifically catered to leverage openapi API.

arrow-up-right arrow-up-right

Summary

Table of Contents

SDK Installation

The SDK can be installed with either npmarrow-up-right, pnpmarrow-up-right, bunarrow-up-right or yarnarrow-up-right package managers.

NPM

PNPM

Bun

Yarn

[!NOTE] This package is published with CommonJS and ES Modules (ESM) support.

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

Name
Type
Scheme

bearerAuth

http

HTTP Bearer

To authenticate with the API the bearerAuth parameter must be set when initializing the SDK client instance. For example:

Available Resources and Operations

chevron-rightAvailable methodshashtag

  • list - List all Audit Logs

  • export - Initiate an asynchronous export of audit logs based on the provided filters. The export file will be generated and available for download. Use 'Get details of Audit Logs export history by ID' API to retrieve the download URL.

  • listExportHistory - List all Audit Logs export history

  • getById - Get audit log by ID

AuditLogs.ExportHistory

  • get - Get details of Audit Logs export history by ID

  • listByTeam - Get Escalation Policy By team

  • create - Create Escalation Policies

  • remove - Remove Escalation Policy

  • getById - Get Escalation Policy By ID

  • update - Update Escalation Policy

  • list - List Global Event Rules

  • create - Create Global Event Rule

  • deleteById - Delete Global Event Rule by ID

  • getById - Get Global Event Rule by ID

  • updateById - Update Global Event Rule by ID

GlobalEventRules.Rulesets

GlobalEventRules.Rulesets.Rules

  • delete - Delete Global Oncall Reminder Rules

  • get - Get Global Oncall Reminder Rules

  • create - Create Global Oncall Reminder Rules

  • update - Update Global Oncall Reminder Rules

  • rebuild - Rebuild a Project In CircleCI

Incidents.Actions.JiraCloud

Incidents.AdditionalResponders

  • add - Add Additional Responders

Incidents.AutoPauseTransientAlerts

Incidents.CommunicationCards

  • create - Create Communication Card

Incidents.Events

  • list - Get Incident Events

Incidents.Notes

Incidents.Postmortems

Incidents.Snooze

  • set - Snooze Incident Notifications

Incidents.Tags

  • list - List Status Page Issue States

  • list - List Overrides

Schedules.Actions

Schedules.Export

Schedules.Overrides

  • create - Create Schedule Override

  • update - Update Schedule Override

Schedules.Rotations

Services.Overlays.CustomContent

Services.Overlays.DedupKey

  • delete - Delete Dedup Key Overlay

Squads.Members

StatusPages.ComponentGroups

  • list - List Component Groups

  • create - Create Component Group

  • deleteById - Delete Component Group By ID

  • getById - Get Component Group By ID

StatusPages.Components

StatusPages.Issues

StatusPages.Maintenances

  • list - List Subscribers

  • getById - Get Workflow Action By ID

  • get - Get Workflow Logs

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.

chevron-rightAvailable standalone functionshashtag

Pagination

Some of the endpoints in this SDK support pagination. To use pagination, you make your SDK calls as usual, but the returned response object will also be an async iterable that can be consumed using the for await...ofarrow-up-right syntax.

Here's an example of one such pagination call:

File uploads

Certain SDK methods accept files as part of a multi-part request. It is possible and typically recommended to upload files as a stream rather than reading the entire contents into memory. This avoids excessive memory consumption and potentially crashing with out-of-memory errors when working with very large files. The following example demonstrates how to attach a file stream to a request.

[!TIP]

Depending on your JavaScript runtime, there are convenient utilities that return a handle to a file without reading the entire contents into memory:

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:

Error Handling

SquadcastSDKErrorarrow-up-right is the base class for all HTTP error responses. It has the following properties:

Property
Type
Description

error.message

string

Error message

error.statusCode

number

HTTP response status code eg 404

error.headers

Headers

HTTP response headers

error.body

string

HTTP body. Can be empty string if no body is returned.

error.rawResponse

Response

Raw HTTP response

error.data$

Optional. Some errors may contain structured data. See Error Classes.

Example

Error Classes

Primary errors:

chevron-rightLess common errors (9)hashtag

Network errors:

Inherit from SquadcastSDKErrorarrow-up-right:

  • CommonV4Errorarrow-up-right: The server could not understand the request due to invalid syntax. Applicable to 32 of 230 methods.*

  • ResponseBodyError1arrow-up-right: Represents a CircleCI error response for a 400 status code. Status code 400. Applicable to 1 of 230 methods.*

  • ResponseBodyError2arrow-up-right: Represents a CircleCI error response for a 400 status code. Status code 400. Applicable to 1 of 230 methods.*

  • ResponseValidationErrorarrow-up-right: Type mismatch between the data returned from the server and the structure expected by the SDK. See error.rawValue for the raw value and error.pretty() for a nicely formatted multi-line string.

* Check the method documentation to see if the error is applicable.

Server Selection

Override Server URL Per-Client

The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:

Custom HTTP Client

The TypeScript SDK makes API calls using an HTTPClient that wraps the native Fetch APIarrow-up-right. This client is a thin wrapper around fetch and provides the ability to attach hooks around the request lifecycle that can be used to modify the request or handle errors and response.

The HTTPClient constructor takes an optional fetcher argument that can be used to integrate a third-party HTTP client or when writing tests to mock out the HTTP client and feed in fixtures.

The following example shows how to use the "beforeRequest" hook to to add a custom header and a timeout to requests and how to use the "requestError" hook to log errors:

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass a logger that matches console's interface as an SDK option.

[!WARNING] Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.

Development

Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

Last updated