Maplerad SDK

Appearance

Maplerad SDKNodeJs SDK for Maplerad API

Type-safe, modern SDK for integrating Maplerad payments, collections, wallets, cards, and identity services into your Node.js applications.

Get Started
API Overview
🚀

Broad API Coverage

Customers, wallets, transfers, virtual accounts, bills, FX, crypto, issuing, subscriptions, and supporting lookup endpoints are available through one SDK.

🔒

Type-Safe

Generated request and response types are exported from the package so you can build against the Maplerad schema with autocomplete and compile-time checks.

🎯

Intuitive API

Use createClient for quick runtime setup or Core when you want an explicit class instance with the same API binder underneath.

📦

Lightweight Setup

The included oapiex configuration can be as minimal as a client secret and environment while still allowing you to grow into advanced options later.

🛡️

Configurable Auth

The SDK kit supports bearer, apiKey, basic, oauth2, and custom authentication strategies through a consistent options object.

📖

Context-Rich Docs

The documentation explains what each API namespace is for, when to use it, and how the generated methods map to the underlying endpoints.

Quick Start ​

Installation ​

bash
pnpm add maplerad-sdk
bash
npm install maplerad-sdk
bash
yarn add maplerad-sdk
ts
import { createClient } from 'maplerad-sdk';

const sdk = createClient({
  environment: 'sandbox',
  clientSecret: process.env.MAPLERAD_CLIENT_SECRET!,
});

const wallets = await sdk.api.wallets.list();

Why Use This SDK? ​

This SDK is designed for teams that want a direct, typed integration with the Maplerad API:

  • TypeScript-first request and response models
  • A consistent sdk.api.* surface across product areas
  • Minimal setup for local development and test environments
  • Enough low-level exports for teams that want to build wrappers or shared abstractions
  • Generated JSDoc on the API classes that keeps the docs grounded in the source API description

What You Get ​

  • A createClient() helper for quickly bootstrapping the SDK.
  • A Core class if you prefer explicit instances.
  • Generated API namespaces under sdk.api.*.
  • Schema-derived request and response types exported from Schema.

Use the guide to get configured, then move to the API section when you need namespace-level behavior and endpoint context.