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

@bisibility/sdk

v0.7.3

Published

TypeScript client for the Bisibility API - SEO rank tracking, keywords, and ranking history.

Downloads

2,984

Readme

@bisibility/sdk

Part of bisibility - open-source keyword rank tracking you can self-host and automate. This repository contains the TypeScript SDK for the Bisibility REST API.

Docs · API reference · Roadmap

Status: Published on npm as v0.6.1.

TypeScript SDK for the Bisibility REST API.

Requirements

  • Node.js >= 18 (the SDK uses the global fetch, Headers, and AbortSignal APIs).
  • The package is ESM-only ("type": "module"). Use import; there is no CommonJS build. From CommonJS you can use await import("@bisibility/sdk").
  • On runtimes without a global fetch (or to use a custom HTTP stack), inject your own implementation via the fetch config option (see Configuration).

Install

npm install @bisibility/sdk

Quickstart

import { BisibilityClient } from "@bisibility/sdk";

const bisibility = new BisibilityClient({
  apiKey: process.env.BISIBILITY_API_KEY
});

const projects = await bisibility.projects.list();
const projectId = projects.data[0]?.id;

if (projectId) {
  const created = await bisibility.keywords.add(projectId, {
    keywords: [
      {
        keyword: "rank tracker api",
        target_url: "https://example.com/rank-tracker",
        tags: ["api"]
      }
    ]
  });

  const keywordId = created.results[0]?.keyword.id;
  if (keywordId) {
    const check = await bisibility.rankChecks.run(keywordId);
    console.log(check.position, check.ranking_url);
  }
}

Configuration

const bisibility = new BisibilityClient({
  apiKey: "bsb_key_live_...",
  baseUrl: "https://bisibility.com/api/v1"
});

baseUrl should point at the API v1 root. For self-hosted installs, pass your own https://your-host.example/api/v1 URL. Browser apps may pass a relative URL such as /api/v1.

The client accepts project API keys (bsb_key_live_... or bsb_key_test_...) and personal access tokens (bsb_pat_live_...). Retired bsk_ and bsp_ credentials are rejected locally. For a PAT with multiple project memberships, set projectId to send X-Bisibility-Project on project-implicit routes:

const bisibility = new BisibilityClient({
  apiKey: process.env.BISIBILITY_PERSONAL_ACCESS_TOKEN,
  projectId: process.env.BISIBILITY_PROJECT_ID
});

const me = await bisibility.account.get();
const project = await bisibility.projects.create({ domain: "example.com", name: "Example" });
await bisibility.apiKeys.create({ name: "CI" }, { projectId: project.id });

OAuth clients can pass their opaque bearer token as accessToken. It is mutually exclusive with apiKey and does not use API key prefix validation:

const bisibility = new BisibilityClient({
  accessToken: oauth.accessToken,
});

A custom fetch implementation can be injected for older runtimes, proxies, or testing:

const bisibility = new BisibilityClient({
  apiKey: "bsb_key_live_...",
  fetch: myFetch
});

Protected methods send the configured apiKey or accessToken as Authorization: Bearer <token>. Write methods accept an optional idempotencyKey request option, which maps to the server Idempotency-Key header. Requests set redirect: "error" so credentials are never forwarded through an HTTP redirect. Custom fetch implementations should preserve that behavior.

Requests identify the package with X-Bisibility-Client: bisibility-sdk-ts/<version> and, where the runtime permits, the same value as User-Agent. Inputs mirror JSON wire names, so payload fields use snake_case (for example tracking_scope and expires_in_days). SDK-only configuration and request options remain camelCase.

Idempotent requests retry network errors and HTTP 429/503 responses twice by default. GET, HEAD, PUT, and DELETE are idempotent; any request carrying an idempotencyKey is also retryable. Set maxRetries: 0 to disable retries. Exponential backoff starts at 500ms, and Retry-After is honored up to 60 seconds.

Every method accepts per-request options:

await bisibility.projects.list({
  headers: { "X-Request-Id": "..." },
  signal: controller.signal, // your own AbortSignal
  timeout: 10_000 // ms; composed with `signal` when both are set
});

Without an explicit timeout or signal, every attempt has a 30-second timeout. Set timeout: null on the client or an individual request to opt out.

API version compatibility

The SDK declares Bisibility-API-Version: v1 on every request. Before its first ordinary API operation, each client lazily checks /capabilities once; calling getCapabilities() first satisfies the same check without a duplicate request. A server that advertises apiVersions but does not serve v1 fails with BisibilityApiVersionError before the requested operation runs. Older servers whose capabilities response has no apiVersions field remain compatible, and the original request continues normally.

Public resource IDs

Every resource identifier accepted or returned by the SDK uses public ID v3. The format is a lowercase resource prefix, an underscore, and a 24-character CUID2 suffix: prefix_[a-z][a-z0-9]{23}. For example, a project ID is prj_a1b2c3d4e5f6g7h8j9k0m2n3 and a keyword ID is kw_b2c3d4e5f6g7h8j9k0m2n3p4.

The SDK rejects raw database IDs, legacy IDs, mixed-case values, and a valid ID with the wrong resource prefix before sending a request. PUBLIC_ID_PREFIXES, isPublicIdOfType, and resource-specific types such as ProjectId, KeywordId, and WebhookId are exported for callers that build typed integrations.

Locations are identified by location_key; they do not expose a location ID. Cloud import and export payloads use schema version 5 only. Pagination cursors are opaque SDK values; v3 API cursors returned by the server must be passed back unchanged.

Resource namespaces

The client groups operations by resource. Existing flat methods remain available as deprecated compatibility delegates until 1.0.

| Namespace | Methods | | - | - | | system | getHealth, getLiveness, getReadiness, getCapabilities, getOpenApi, getLlmsText | | pricing | getRates, estimate | | locations | search | | account | get, update, plus tokens.list, tokens.create, tokens.revoke | | projects | list, create, get, update, delete, getDefaults, updateDefaults | | apiKeys | list, iterate, create, revoke | | webhooks | list, iterate, create, update, delete | | keywords | list, iterate, add, get, update, setTargetUrl, delete, bulkUpdate, match, research, plus suggestions.list, metrics.get | | backlinks | analyze, extendSnapshot | | rankChecks | list, iterate, run, getResult, plus history.export, history.iterate | | sitemapMonitors | list, update | | signals | list, iterate, create | | analytics | overview.get, traffic.list, traffic.sync, searchPerformance.list | | alertRules | list, iterate, create, update, delete | | alerts | list, iterate, mute, markAllRead | | notificationSettings | get, update | | team | members.* and invites.* | | providers | list, iterate, connect, test, updateSettings, setEnabled, setPriority, setPrimary, disconnect | | savedViews | list, iterate, create, delete | | competitors | list, iterate, add, remove | | imports | runFromExport, plus compatibility.*, tokens.*, sessions.* |

apiKeys.list() and apiKeys.create() use the current project selected by authentication. Pass { projectId } to select the explicit project route. A personal access token spanning multiple projects must pass projectId because the top-level route cannot select a project unambiguously.

List methods return { data, meta } with meta.next_cursor. Resource methods return the resource object directly, matching the Bisibility API response shape.

Every cursor-paginated list has an iterate* counterpart that preserves filters and yields items across all pages:

for await (const keyword of bisibility.keywords.iterate(projectId, { device: "desktop" })) {
  console.log(keyword.text);
}

The same pattern is available for rank checks, signals, API keys (including project API keys), webhooks, alert rules, triggered alerts, team members, team invites, providers, saved views, competitors, and migration tokens. iterateCursorPagination is exported for custom paginated endpoints.

Keyword research and metrics

keywords.research runs a paid, cached DataForSEO lookup for one seed. Select the research depth up front with resultLimit; this endpoint does not use offset pagination. It requires API write scope because a cache miss can spend the project's provider budget:

const research = await bisibility.keywords.research(projectId, {
  seed: "rank tracker",
  mode: "auto",
  resultLimit: 300,
  includeClickstream: false,
  maxCostCents: 5
});

Set estimateOnly: true for a free cache-aware dry run before a cost-sensitive request. Source diagnostics report ok, failed, or skipped, with a machine-readable reason when applicable.

keywords.metrics.get hydrates provider metrics for one to 700 keywords. Its input mirrors the API request body, cached rows do not contribute to cost_cents, and API write scope is required:

const metrics = await bisibility.keywords.metrics.get(projectId, {
  keywords: ["rank tracker", "seo api"],
  include_clickstream: false,
  estimate_only: true,
  max_cost_cents: 5
});

An estimate response includes cached_count, fetched_count_estimate, and estimated_cost_cents, and never calls the provider or spends budget.

Search volume, CPC, competition, difficulty, intent, and monthly trend values can be null when a provider market does not supply them.

Project defaults

projects.updateDefaults(projectId, patch) sends PATCH /projects/{id}/defaults and returns the persisted ProjectDefaults (default market, schedule, and timezone for new keywords):

await bisibility.projects.updateDefaults(projectId, {
  country: "United States",
  device: "desktop",
  frequency: "daily"
});

Asynchronous rank checks

rankChecks.run runs synchronously by default. Pass async: true to enqueue the check instead; the server responds 202 with a RankCheck in status: "running" that you can poll via getRankCheckResult:

const queued = await bisibility.rankChecks.run(keywordId, undefined, { async: true });
// queued.status === "running"
const result = await bisibility.rankChecks.getResult(queued.id);

Failed checks carry status: "failed", an error message, and provider fallback attempts.

Signals

signals.create ingests a signal (POST /signals) into the project tied to your API key; source must be "deploy", "cms", or "api", and type follows the category.event pattern (for example deploy.completed). listSignals(projectId, options) pages through a project's signals newest first with optional source, type, from, and to filters:

await bisibility.signals.create({
  source: "deploy",
  type: "deploy.completed",
  payload: { version: "1.2.3" }, // <= 8KB serialized
  url: "https://example.com/releases/1"
});

const recent = await bisibility.signals.list(projectId, {
  source: "deploy",
  from: "2026-07-01T00:00:00.000Z"
});

Public cost estimates

pricing.getRates and pricing.estimate are anonymous and work without an apiKey:

const rates = await bisibility.pricing.getRates();
const estimate = await bisibility.pricing.estimate({
  keywords: 250,
  frequency: "daily",
  provider: "dataforseo",
  option: "standard"
});
// estimate.data.monthly_cost_usd

Errors

All SDK errors extend BisibilityError; its concrete subclasses are BisibilityApiError, BisibilityApiVersionError, BisibilityConfigurationError, BisibilityNetworkError, and BisibilityResponseError. BisibilityApiVersionError also extends BisibilityApiError and exposes the declared version as declaredApiVersion plus the server advertisement as serverApiVersions. The original RFC problem details body is available on API errors as error.problem. API errors also provide isRateLimit, isNotFound, and retryAfterSeconds. error.headers retains ordinary response headers while credential and cookie headers are removed before the error is exposed to application logs.

import { BisibilityApiError, BisibilityApiVersionError } from "@bisibility/sdk";

try {
  await bisibility.keywords.get("kw_z9y8x7w6v5u4t3s2r1q0p9n8");
} catch (error) {
  if (error instanceof BisibilityApiVersionError) {
    console.error(error.declaredApiVersion, error.serverApiVersions);
  } else if (error instanceof BisibilityApiError) {
    console.error(error.status, error.problem?.detail);
  }
}

Contributing and security

See CONTRIBUTING.md for the development workflow and SECURITY.md for private vulnerability reporting. Changes are recorded in CHANGELOG.md.

License

Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.