The Intercom TypeScript library provides convenient access to the Intercom APIs from TypeScript.
The TypeScript SDK has been updated to support latest API version (2.11).
npm i -s intercom-clientA full reference for this library is available here.
Instantiate and use the client with the following:
import{IntercomClient}from"intercom-client";constclient=newIntercomClient({token: "YOUR_TOKEN"});awaitclient.aiContent.createContentImportSource({url: "https://www.example.com"});The SDK exports all request and response types as TypeScript interfaces. Simply import them with the following namespace:
import{Intercom}from"intercom-client";constrequest: Intercom.ConfigureAwayAdminRequest={
...
};When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.
import{IntercomError}from"intercom-client";try{awaitclient.aiContent.createContentImportSource(...);}catch(err){if(errinstanceofIntercomError){console.log(err.statusCode);console.log(err.message);console.log(err.body);console.log(err.rawResponse);}}List endpoints are paginated. The SDK provides an iterator so that you can simply loop over the items:
import{IntercomClient}from"intercom-client";constclient=newIntercomClient({token: "YOUR_TOKEN"});constpageableResponse=awaitclient.articles.list();forawait(constitemofpageableResponse){console.log(item);}// Or you can manually iterate page-by-pageletpage=awaitclient.articles.list();while(page.hasNextPage()){page=page.getNextPage();}// You can also access the underlying responseconstresponse=page.response;If you would like to send additional headers as part of the request, use the headers request option.
constresponse=awaitclient.aiContent.createContentImportSource(...,{headers: {'X-Custom-Header': 'custom value'}});If you would like to send additional query string parameters as part of the request, use the queryParams request option.
constresponse=awaitclient.aiContent.createContentImportSource(...,{queryParams: {'customQueryParamKey': 'custom query param value'}});The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
A request is deemed retryable when any of the following HTTP status codes is returned:
Use the maxRetries request option to configure this behavior.
constresponse=awaitclient.aiContent.createContentImportSource(...,{maxRetries: 0// override maxRetries at the request level});The SDK defaults to a 60 second timeout. Use the timeoutInSeconds option to configure this behavior.
constresponse=awaitclient.aiContent.createContentImportSource(...,{timeoutInSeconds: 30// override timeout to 30s});The SDK allows users to abort requests at any point by passing in an abort signal.
constcontroller=newAbortController();constresponse=awaitclient.aiContent.createContentImportSource(...,{abortSignal: controller.signal});controller.abort();// aborts the requestThe SDK provides access to raw response data, including headers, through the .withRawResponse() method.
The .withRawResponse() method returns a promise that results to an object with a data and a rawResponse property.
const{ data, rawResponse }=awaitclient.aiContent.createContentImportSource(...).withRawResponse();console.log(data);console.log(rawResponse.headers['X-My-Header']);The SDK supports logging. You can configure the logger by passing in a logging object to the client options.
import{IntercomClient,logging}from"intercom-client";constclient=newIntercomClient({
...
logging: {level: logging.LogLevel.Debug,// defaults to logging.LogLevel.Infologger: newlogging.ConsoleLogger(),// defaults to ConsoleLoggersilent: false,// defaults to true, set to false to enable logging}});The logging object can have the following properties:
level: The log level to use. Defaults tologging.LogLevel.Info.logger: The logger to use. Defaults to alogging.ConsoleLogger.silent: Whether to silence the logger. Defaults totrue.
The level property can be one of the following values:
logging.LogLevel.Debuglogging.LogLevel.Infologging.LogLevel.Warnlogging.LogLevel.Error
To provide a custom logger, you can pass in an object that implements the logging.ILogger interface.
Custom logger examples
Here's an example using the popular winston logging library.
importwinstonfrom'winston';constwinstonLogger=winston.createLogger({...});constlogger: logging.ILogger={debug: (msg, ...args)=>winstonLogger.debug(msg, ...args),info: (msg, ...args)=>winstonLogger.info(msg, ...args),warn: (msg, ...args)=>winstonLogger.warn(msg, ...args),error: (msg, ...args)=>winstonLogger.error(msg, ...args),};Here's an example using the popular pino logging library.
importpinofrom'pino';constpinoLogger=pino({...});constlogger: logging.ILogger={debug: (msg, ...args)=>pinoLogger.debug(args,msg),info: (msg, ...args)=>pinoLogger.info(args,msg),warn: (msg, ...args)=>pinoLogger.warn(args,msg),error: (msg, ...args)=>pinoLogger.error(args,msg),};The SDK works in the following runtimes:
- Node.js 18+
- Vercel
- Cloudflare Workers
- Deno v1.25+
- Bun 1.0+
- React Native
The SDK provides a way for you to customize the underlying HTTP client / Fetch function. If you're running in an unsupported environment, this provides a way for you to break glass and ensure the SDK works.
import{IntercomClient}from"intercom-client";constclient=newIntercomClient({
...
fetcher: // provide your implementation here});While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!