Ding Typescript/Javascript SDK

The Ding Typescript library provides convenient access to the Ding API from applications written in JS or TS.

Summary

Ding: The OTP API allows you to send authentication codes to your users using their phone numbers.

Table of Contents

* Ding Typescript/Javascript SDK
* SDK Installation
* SDK Example Usage
* Available Resources and Operations
* Error Handling
* Custom HTTP Client
* Authentication
* Server Selection
* Requirements
* Retries
* Debugging
* Standalone functions
* Development
* Maturity
* Contributions

SDK Installation

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

$3

``bash
npm add @ding-live/ding
`

$3

`bash
pnpm add @ding-live/ding
`

$3

`bash
bun add @ding-live/ding
`

$3

`bash
yarn add @ding-live/ding zod

Note that Yarn does not install peer dependencies automatically. You will need

to install zod as shown above.

`

$3

This SDK is also an installable MCP server where the various SDK methods are
exposed as tools that can be invoked by AI applications.

> Node.js v20 or greater is required to run the MCP server from npm.

Claude installation steps

Add the following server definition to your claude_desktop_config.json file:

`json
{
"mcpServers": {
"Ding": {
"command": "npx",
"args": [
"-y", "--package", "@ding-live/ding",
"--",
"mcp", "start",
"--api-key", "..."
]
}
}
}
`

Cursor installation steps

Create a .cursor/mcp.json file in your project root with the following content:

`json
{
"mcpServers": {
"Ding": {
"command": "npx",
"args": [
"-y", "--package", "@ding-live/ding",
"--",
"mcp", "start",
"--api-key", "..."
]
}
}
}
`

You can also run MCP servers as a standalone binary with no additional dependencies. You must pull these binaries from available Github releases:

`bash
curl -L -o mcp-server \
https://github.com/{org}/{repo}/releases/download/{tag}/mcp-server-bun-darwin-arm64 && \
chmod +x mcp-server
`

If the repo is a private repo you must add your Github PAT to download a release -H "Authorization: Bearer {GITHUB_PAT}".


`json
{
"mcpServers": {
"Todos": {
"command": "./DOWNLOAD/PATH/mcp-server",
"args": [
"start"
]
}
}
}
`

For a full list of server arguments, run:

`sh
npx -y --package @ding-live/ding -- mcp start --help
`





SDK Example Usage

$3

Send an OTP code to a user's phone number.

`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.createAuthentication({
customerUuid: "cf2edc1c-7fc6-48fb-86da-b7508c6b7b71",
locale: "fr-FR",
phoneNumber: "+1234567890",
});

// Handle the result
console.log(result);
}

run();

`

$3

Check that a code entered by a user is valid.

`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.check({
authenticationUuid: "eebe792b-2fcc-44a0-87f1-650e79259e02",
checkCode: "123456",
customerUuid: "64f66a7c-4b2c-4131-a8ff-d5b954cca05f",
});

// Handle the result
console.log(result);
}

run();

`

$3

Perform a retry if a user has not received the code.

`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.retry();

// Handle the result
console.log(result);
}

run();

`

$3

Send feedback about the authentication process.


`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.feedback({
customerUuid: "cc0f6c04-40de-448f-8301-3cb0e6565dff",
phoneNumber: "+1234567890",
status: "onboarded",
});

// Handle the result
console.log(result);
}

run();

`

$3

Get the status of an authentication.

`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.getAuthenticationStatus(
"d8446450-f2fa-4dd9-806b-df5b8c661f23",
);

// Handle the result
console.log(result);
}

run();

`

$3

Perform a phone number lookup.

`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.lookup.lookup(
"69a197d9-356c-45d1-a807-41874e16b555",
"",
);

// Handle the result
console.log(result);
}

run();

`





Available Resources and Operations

Available methods

$3

* lookup - Look up for phone number

$3

* check - Check a code
* createAuthentication - Send a code
* feedback - Send feedback
* getAuthenticationStatus - Get authentication status
* retry - Perform a retry

Error Handling

Some methods specify known errors which can be thrown. All the known errors are enumerated in the models/errors/errors.ts module. The known errors for a method are documented under the Errors tables in SDK docs. For example, the check method may throw the following errors:

| Error Type | Status Code | Content Type |
| -------------------- | ----------- | ---------------- |
| errors.ErrorResponse | 400 | application/json |
| errors.SDKError | 4XX, 5XX | \/\ |

If the method throws an error and it is not captured by the known errors, it will default to throwing a SDKError.

`typescript
import { Ding } from "@ding-live/ding";
import {
ErrorResponse,
SDKValidationError,
} from "@ding-live/ding/models/errors";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
let result;
try {
result = await ding.otp.check({
authenticationUuid: "eebe792b-2fcc-44a0-87f1-650e79259e02",
checkCode: "123456",
customerUuid: "64f66a7c-4b2c-4131-a8ff-d5b954cca05f",
});

// Handle the result
console.log(result);
} catch (err) {
switch (true) {
// The server response does not match the expected SDK schema
case (err instanceof SDKValidationError): {
// Pretty-print will provide a human-readable multi-line error message
console.error(err.pretty());
// Raw value may also be inspected
console.error(err.rawValue);
return;
}
case (err instanceof ErrorResponse): {
// Handle err.data$: ErrorResponseData
console.error(err);
return;
}
default: {
// Other errors such as network errors, see HTTPClientErrors for more details
throw err;
}
}
}
}

run();

`

Validation errors can also occur when either method arguments or data returned from the server do not match the expected format. The SDKValidationError that is thrown as a result will capture the raw value that failed validation in an attribute called rawValue. Additionally, a pretty() method is available on this error that can be used to log a nicely formatted multi-line string since validation errors can list many issues and the plain error string may be difficult read when debugging.

In some rare cases, the SDK can fail to get a response from the server or even make the request due to unexpected circumstances such as network conditions. These types of errors are captured in the models/errors/httpclienterrors.ts module:

| HTTP Client Error | Description |
| ---------------------------------------------------- | ---------------------------------------------------- |
| RequestAbortedError | HTTP request was aborted by the client |
| RequestTimeoutError | HTTP request timed out due to an AbortSignal signal |
| ConnectionError | HTTP client was unable to make a request to a server |
| InvalidRequestError | Any input used to create a request is invalid |
| UnexpectedClientError | Unrecognised or unexpected error |





Custom HTTP Client

The TypeScript SDK makes API calls using an HTTPClient that wraps the native
Fetch API. 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:

`typescript
import { Ding } from "@ding-live/ding";
import { HTTPClient } from "@ding-live/ding/lib/http";

const httpClient = new HTTPClient({
// fetcher takes a function that has the same signature as native fetch.
fetcher: (request) => {
return fetch(request);
}
});

httpClient.addHook("beforeRequest", (request) => {
const nextRequest = new Request(request, {
signal: request.signal || AbortSignal.timeout(5000)
});

nextRequest.headers.set("x-custom-header", "custom value");

return nextRequest;
});

httpClient.addHook("requestError", (error, request) => {
console.group("Request Error");
console.log("Reason:", ${error});
console.log("Endpoint:", ${request.method} ${request.url});
console.groupEnd();
});

const sdk = new Ding({ httpClient });
`





Authentication

$3

This SDK supports the following security scheme globally:

| Name | Type | Scheme |
| -------- | ------ | ------- |
| apiKey | apiKey | API key |

To authenticate with the API the apiKey parameter must be set when initializing the SDK client instance. For example:
`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.check({
authenticationUuid: "eebe792b-2fcc-44a0-87f1-650e79259e02",
checkCode: "123456",
customerUuid: "64f66a7c-4b2c-4131-a8ff-d5b954cca05f",
});

// Handle the result
console.log(result);
}

run();

`





Server Selection

$3

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:
`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
serverURL: "https://api.ding.live/v1",
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.check({
authenticationUuid: "eebe792b-2fcc-44a0-87f1-650e79259e02",
checkCode: "123456",
customerUuid: "64f66a7c-4b2c-4131-a8ff-d5b954cca05f",
});

// Handle the result
console.log(result);
}

run();

`





Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.





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:
`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.check({
authenticationUuid: "eebe792b-2fcc-44a0-87f1-650e79259e02",
checkCode: "123456",
customerUuid: "64f66a7c-4b2c-4131-a8ff-d5b954cca05f",
}, {
retries: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});

// Handle the result
console.log(result);
}

run();

`

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:
`typescript
import { Ding } from "@ding-live/ding";

const ding = new Ding({
retryConfig: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
apiKey: "YOUR_API_KEY",
});

async function run() {
const result = await ding.otp.check({
authenticationUuid: "eebe792b-2fcc-44a0-87f1-650e79259e02",
checkCode: "123456",
customerUuid: "64f66a7c-4b2c-4131-a8ff-d5b954cca05f",
});

// Handle the result
console.log(result);
}

run();

`





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.

`typescript
import { Ding } from "@ding-live/ding";

const sdk = new Ding({ debugLogger: console });
`





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.

Available standalone functions

- lookupLookup - Look up for phone number
- otpCheck - Check a code
- otpCreateAuthentication - Send a code
- otpFeedback - Send feedback
- otpGetAuthenticationStatus - Get authentication status
- otpRetry` - Perform a retry

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.
Feel free to open a PR or a Github issue as a proof of concept and we'll do our best to include it in a future release!