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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@vapi-ai/api

v0.1.0

Published

[![npm shield](https://img.shields.io/npm/v/@fern-api/vapi)](https://www.npmjs.com/package/@fern-api/vapi) [![fern shield](https://img.shields.io/badge/%F0%9F%8C%BF-SDK%20generated%20by%20Fern-brightgreen)](https://github.com/fern-api/fern)

Downloads

5

Readme

Vapi Node API Library

npm shield fern shield

The Vapi Node.js library provides convenient access to the Vapi API from JavaScript/TypeScript.

Documentation

API reference documentation is available here.

Installation

npm install --save @fern-api/vapi
# or
yarn add @fern-api/vapi

Usage

import { VapiClient } from @fern-api/vapi;

const vapi = new VapiClient({
  token: "YOUR_API_KEY",
});

const call = await vapi.call.createPhoneCall({
  phoneNumberId: "002-003-0004",
  customerPhoneNumber: "1-800-948-8488",
});

console.log(`Scheduled a call to Pizza Hut! The agent id is ${call.agentId}`);

Handling errors

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

try {
  await vapi.call.createPhoneCall(...);
} catch (err) {
  if (err instanceof VapiError) {
    console.log(err.statusCode);
    console.log(err.message);
    console.log(err.body);
  }
}

Retries

409 Conflict, 429 Rate Limit, and >=500 Internal errors will all be retried twice with exponential bakcoff. You can use the maxRetries option to configure this behavior:

const sites = await vapi.call.get("call-id", {
    maxRetries: 0, // disable retries
});

Timeouts

By default, the SDK has a timeout of 60s. You can use the timeoutInSeconds option to configure this behavior

const sites = await vapi.call.get("call-id", {
    timeoutInSeconds: 10, // timeout after 10 seconds
});

Beta status

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning the package version to a specific version in your package.json file. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributing

While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library 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 README are always very welcome!