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

@harveys-software/zoho-auth-client

v0.1.3

Published

Zoho OAuth client.

Readme

@harveys-software/zoho-auth-client

A small TypeScript client for Zoho OAuth flows.

It currently supports:

  • Server-based authorization code flow
  • Device flow for non-browser apps
  • Refresh token exchange shared across both flows
  • Typed Zoho auth errors via ZohoAuthError

Install

npm install @harveys-software/zoho-auth-client

Build

npm run build

Test

npm test

Requirements

  • Node.js 18+ or another runtime with a global fetch implementation
  • A Zoho OAuth client ID and client secret
  • The correct Zoho data center, for example eu, com, or in

Usage

import { ZohoAuthClient } from "@harveys-software/zoho-auth-client";

const client = new ZohoAuthClient({
  dataCenter: "eu",
  credentials: {
    clientId: process.env.ZOHO_CLIENT_ID!,
    clientSecret: process.env.ZOHO_CLIENT_SECRET!,
  },
});

Constructor signature:

new ZohoAuthClient(config, maxPollingRetries?, pollingInterval?)

Server App Flow

Use serverApp for the authorization code flow.

1. Build the authorization URL

const authorizationUrl = await client.serverApp.getAuthorizationCodeUrl(
  ["AaaServer.profile.Read"],
  "https://example.com/oauth/callback",
  "offline",
  "consent",
);

2. Exchange the authorization code for tokens

const tokenResponse = await client.serverApp.getAccessToken(
  authorizationCode,
  "https://example.com/oauth/callback",
);

console.log(tokenResponse.access_token);
console.log(tokenResponse.refresh_token);

Non-Browser App Flow

Use nonBrowserApp for the device flow.

1. Initiate device authorization

const initiation = await client.nonBrowserApp.deviceInitiationRequest([
  "AaaServer.profile.Read",
]);

console.log(initiation.user_code);
console.log(initiation.device_code);
console.log(initiation.verification_url);

2. Poll for tokens

const tokenResponse = await client.nonBrowserApp.devicePollingRequest(
  initiation.device_code,
);

console.log(tokenResponse.access_token);
console.log(tokenResponse.refresh_token);

Polling automatically handles:

  • authorization_pending
  • slow_down
  • retry exhaustion based on the configured retry limit

Refresh Tokens

refreshTokenRequest stays at the client root because it is shared across both flows.

const refreshed = await client.refreshTokenRequest(refreshToken);

console.log(refreshed.access_token);

Error Handling

All normalized auth failures throw ZohoAuthError.

import {
  ZohoAuthError,
  ZohoAuthErrorCode,
} from "@harveys-software/zoho-auth-client";

try {
  await client.refreshTokenRequest(refreshToken);
} catch (error) {
  if (error instanceof ZohoAuthError) {
    if (error.code === ZohoAuthErrorCode.INVALID_CLIENT) {
      console.error("Check your client credentials");
    }

    console.error(error.details);
  }
}

Current exported error codes include:

  • INVALID_CLIENT
  • INVALID_CLIENT_SECRET
  • INVALID_RESPONSE_TYPE
  • INVALID_CODE
  • INVALID_SCOPE
  • INVALID_OAUTH_SCOPE
  • INVALID_REDIRECT_URI
  • BAD_REQUEST
  • GENERAL_ERROR
  • OTHER_DC
  • ACCESS_DENIED
  • EXPIRED
  • POLLING_RETRIES_EXCEEDED
  • UNKNOWN_ERROR

Public API

ZohoAuthClient

  • serverApp.getAuthorizationCodeUrl(scopes, redirectUri, accessType?, prompt?)
  • serverApp.getAccessToken(code, redirectUri)
  • nonBrowserApp.deviceInitiationRequest(scopes)
  • nonBrowserApp.devicePollingRequest(code, retryCount?)
  • refreshTokenRequest(refreshToken)

Types and errors

  • ZohoAuthConfig
  • ZohoAuthError
  • ZohoAuthErrorCode

Development Notes

  • Source exports are defined in src/index.ts
  • Tests live under tests/
  • The build uses tsup