Chrt SDKs

Available SDKs

TypeScript SDK

Installation

$
npm i -s @chrt-inc/typescript-sdk

Usage

Instantiate and use the client with the following:

1
import { ChrtClient } from "@chrt-inc/typescript-sdk";
2
3
const client = new ChrtClient({ token: "YOUR_TOKEN" });
4
await client.root.postAuthd();

Request And Response Types

The SDK exports all request and response types as TypeScript interfaces. Simply import them with the following namespace:

1
import { Chrt } from "@chrt-inc/typescript-sdk";
2
3
const request: Chrt.TemplateReq = {
4
    ...
5
};

Exception Handling

When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.

1
import { ChrtError } from "@chrt-inc/typescript-sdk";
2
3
try {
4
    await client.root.postAuthd(...);
5
} catch (err) {
6
    if (err instanceof ChrtError) {
7
        console.log(err.statusCode);
8
        console.log(err.message);
9
        console.log(err.body);
10
    }
11
}

Advanced

Additional Headers

If you would like to send additional headers as part of the request, use the headers request option.

1
const response = await client.root.postAuthd(..., {
2
    headers: {
3
        'X-Custom-Header': 'custom value'
4
    }
5
});

Retries

The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retriable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).

A request is deemed retriable when any of the following HTTP status codes is returned:

• 408 (Timeout)
• 429 (Too Many Requests)
• 5XX (Internal Server Errors)

Use the maxRetries request option to configure this behavior.

1
const response = await client.root.postAuthd(..., {
2
    maxRetries: 0 // override maxRetries at the request level
3
});

Timeouts

The SDK defaults to a 60 second timeout. Use the timeoutInSeconds option to configure this behavior.

1
const response = await client.root.postAuthd(..., {
2
    timeoutInSeconds: 30 // override timeout to 30s
3
});

Aborting Requests

The SDK allows users to abort requests at any point by passing in an abort signal.

1
const controller = new AbortController();
2
const response = await client.root.postAuthd(..., {
3
    abortSignal: controller.signal
4
});
5
controller.abort(); // aborts the request

Runtime Compatibility

The SDK defaults to node-fetch but will use the global fetch client if present. The SDK works in the following runtimes:

• Node.js 18+
• Vercel
• Cloudflare Workers
• Deno v1.25+
• Bun 1.0+
• React Native

Customizing Fetch Client

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.

1
import { ChrtClient } from "@chrt-inc/typescript-sdk";
2
3
const client = new ChrtClient({
4
    ...
5
    fetcher: // provide your implementation here
6
});

Example

Here’s a practical example of integrating the Chrt SDK in a Next.js application with authentication:

Setting up the Client with Authentication

Create a utility function to handle client instantiation with dynamic authentication:

1
// app/providers/ChrtClient/getChrtClient.ts
2
import "server-only";
3
import { ChrtClient } from "@chrt-inc/typescript-sdk";
4
import { auth } from "@clerk/nextjs/server";
5
6
export async function getChrtClient(): Promise<ChrtClient> {
7
  const { getToken } = await auth();
8
  const token = await getToken();
9
10
  return new ChrtClient({
11
    environment: process.env.NEXT_PUBLIC_CHRT_API_BASE_URL || "https://api.dev.chrt.com",
12
    token: () => token!,
13
  });
14
}

Using the Client in Server Components

1
// app/(app)/orders/page.tsx
2
import { getChrtClient } from "../../app/providers/ChrtClient";
3
4
export default async function OrdersPage() {
5
  const chrt = await getChrtClient();
6
7
  try {
8
    const orders = await chrt.shipping.orders.expanded.listForCourierOperatorsV1();
9
10
    console.log("Orders:", orders);
11
12
    return (
13
      <div>
14
        {/* Render your orders */}
15
      </div>
16
    );
17
  } catch (error) {
18
    console.error("Failed to fetch orders:", error);
19
    return <div>Error loading orders</div>;
20
  }
21
}

Client Provider Setup

For client-side usage, you can also set up a React context provider:

1
// app/providers/ChrtClient/index.ts
2
export { getChrtClient } from "./getChrtClient"; // Server-side utility
3
export { ChrtClientProvider, useChrtClient } from "./ChrtClientProvider"; // Client-side provider

This pattern allows you to seamlessly use the Chrt SDK across your application with proper authentication handling.

Java SDK

Installation

Add the dependency to your pom.xml:

1
<dependency>
2
    <groupId>com.chrt</groupId>
3
    <artifactId>java-sdk</artifactId>
4
    <version>1.689.0</version>
5
</dependency>

Or with Gradle:

1
implementation 'com.chrt:java-sdk:1.689.0'

Pin Java to the same PR-based version as the other SDKs (1.{PR_NUMBER}.{PATCH}), then update deliberately when you are ready for new generated API changes. The Java SDK is generated alongside the TypeScript and Swift SDKs and provides the same API coverage. See the API Reference for full endpoint documentation with Java snippets.

Swift SDK

The Swift SDK is available via Swift Package Manager. Add the following to your Package.swift:

1
.package(url: "https://github.com/chrt-inc/swift-sdk", .upToNextMinor(from: "1.689.0"))

Pin Swift to the same PR-based version as the other SDKs (1.{PR_NUMBER}.{PATCH}). Prefer upToNextMinor if you want patch updates for the same server PR, or an exact version if you want fully locked generated API shapes. The Swift SDK is ideal for building native iOS applications that integrate with CHRT — for example, driver apps that send location updates and complete task artifacts.

Contributing

While we value open-source contributions to these SDKs, the libraries are generated programmatically. Additions made directly 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 READMEs are always very welcome!

For more information about our APIs and integrations, check out our API Reference or contact our Support team.