npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ryftpay/ryft-sdk

v1.5.0

Published

The official Ryft NodeJs SDK

Readme

Ryft Node SDK

build npm version License: MIT

Installation

# with npm
npm install @ryftpay/ryft-sdk

# with yarn
yarn add @ryftpay/ryft-sdk

# with bun
bun add @ryftpay/ryft-sdk

Usage

The SDK must be configured with your account's secret key, available in the Ryft Dashboard. The SDK will automatically determine the environment based on the provided key. For example, sk_sandbox... will point to sandbox, while sk_live will point to production.

Importing the SDK

You can access the SDK and all of the methods and types by importing it as follows:

import { Ryft } from '@ryftpay/ryft-sdk';

Initialising with a secret key

You can pass your secret key via the Config in the SDK constructor. For example:

const ryft = new Ryft({secretKey: 'sk_sandbox_1234567890'});

Initialising with environment variables

You can set the following environment variable, and the SDK will automatically pick it up:

  • RYFT_SECRET_KEY

[!NOTE] If you use env variables you don't have to pass your secret key to the config. This is handled for you

Using Promises and Handling Errors

Every method returns a chainable promise which can be used instead of a regular callback. This allows you to either await for the Promise to resolve or use the then and catch keywords to handle the return.

Example with await and catching the RyftError

try {
    const resp = await ryft.accounts.get('acc_123456789');
} catch (e RyftError) {
    console.log(e)
}

Example with then and catch

ryft.accounts.get('acc_123456789')
    .then((r) => console.log(r))
    .catch((e) => console.log(e));

Basic Example

import { Ryft } from '@ryftpay/ryft-sdk';

const ryft = new Ryft({secretKey: 'sk_sandbox_1234567890'});

ryft.accounts.get('acc_123456789')
    .then((r) => console.log(r))
    .catch((e) => console.log(e));