@or-sdk/sdk-api

@or-sdk/sdk-api

OneReach SDK client for Sdk Api.

When to use

• Use this package when integrating with the Sdk Api capability on the OneReach platform.
• Use its typed client and exported models instead of hand-writing requests to that service.

When not to use

• Do not use it for a different platform capability; choose the dedicated @or-sdk/* package instead.
• Do not use it for generic third-party HTTP calls.

Installation

$ npm i @or-sdk/sdk-api

Usage

import { SdkApi } from '@or-sdk/sdk-api'

// with direct api url
const sdkApi = new SdkApi({
  token: 'my-account-token-string',
  sdkUrl: 'http://example.sdk-api/endpoint'
});

// with service discovery(slower)
const sdkApi = new SdkApi({
  token: 'my-account-token-string',
  discoveryUrl: 'http://example.discovery/endpoint'
});

Configuration

• Prefer sdkUrl when the service URL is known; it avoids a discovery request.
• Use discoveryUrl only when the service URL is not available.
• Provide token as a bearer-token string or getter where supported.

Common pitfalls

• Keep the client token current when it can expire; a token getter is preferable where the constructor accepts one.
• Treat the generated TypeScript types as the authoritative contract for optional parameters and response shapes.

Method map

Method	Purpose
generateLegacyToken(...)	See the exported TypeScript signature for parameters and result.

More detail

Full signatures and exported types are available in src/ and dist/types/.

Additional API reference

Methods below were missing from the package guide. Signatures and return types are taken directly from the exported source API.

SdkApi

Method	Returns	Purpose
makeRequest(params: CalApiParams)	Promise<T>	See the exported TypeScript signature for behavior and constraints.