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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@cvent/sdk

v1.0.6

Published

Developer-friendly & type-safe Typescript SDK specifically catered to leverage *@cvent/sdk* API.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

cpernicano-cventcpernicano-cventjmorley-cventjmorley-cventnoahjohnhaynoahjohnhaycvent-build-and-deploycvent-build-and-deploy

Keywords

Readme

@cvent/sdk

Developer-friendly & type-safe Typescript SDK specifically catered to leverage @cvent/sdk API.

Summary

Cvent REST APIs: # Introduction The Cvent API Platform is built around REST, providing intuitive endpoints to leverage the Cvent platform for your event needs. The APIs use JSON-encoded requests/responses and HTTP codes. Resources are protected using OAuth2.

Getting Started

This SDK is generated by Speakeasy. For usage instructions, refer to the README and USAGE files. To obtain API credentials, visit the Cvent REST API Overview.

The Cvent REST API uses OAuth2 for authorization (client credentials flow).

Endpoints

| Region | Hostname | |:--------------|:-----------------------------------| | North America | https://api-platform.cvent.com | | Europe | https://api-platform-eur.cvent.com |

The current version is ea.

Rate Limits

| Tier | Daily Calls | Calls/Sec | Max Burst | | -------- | ----------- | --------- | --------- | | Free | 1,000 | 2 | 1 | | Standard | 15,000 | 10 | 10 | | Premium | 500,000 | 25 | 25 |

Daily quota resets at 12 midnight UTC. When limits are exceeded, the API returns 429 Too Many Requests. Use exponential backoff to handle rate limit errors.

Filtering

Filter pattern: filter=field comparisonType value

Example: GET /contacts?filter=lastName eq Smith

Versioning

Backward compatible: Adding resources, optional parameters, or attributes.

Backward incompatible: Adding required parameters; deleting resources/attributes; changing data types.

For more documentation, visit developers.cvent.com.

For more information about the API: Cvent Developer Documentation

Table of Contents

SDK Installation

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

NPM

npm add @cvent/sdk

PNPM

pnpm add @cvent/sdk

Bun

bun add @cvent/sdk

Yarn

yarn add @cvent/sdk

[!NOTE] This package is published with CommonJS and ES Modules (ESM) support.

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example

import { CventSDK } from "@cvent/sdk";

const cventSDK = new CventSDK({
  security: {
    oAuth2ClientCredentials: {
      clientID: process.env["CVENTSDK_CLIENT_ID"] ?? "",
      clientSecret: process.env["CVENTSDK_CLIENT_SECRET"] ?? "",
      tokenURL: process.env["CVENTSDK_TOKEN_URL"] ?? "",
      scopes: process.env["CVENTSDK_SCOPES"] ?? "",
    },
  },
});

async function run() {
  const result = await cventSDK.users.getAccountUserGroups({
    token: "1a2b3c4d5e6f7g8h9i10j11k",
    filter: "name eq 'My User Group'",
  });

  for await (const page of result) {
    console.log(page);
  }
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security schemes globally:

| Name | Type | Scheme | Environment Variable | | ------------------------- | ------ | ------------ | ------------------------------------- | | oAuth2ClientCredentials | oauth2 | OAuth2 token | CVENTSDK_O_AUTH2_CLIENT_CREDENTIALS | | oAuth2AuthorizationCode | oauth2 | OAuth2 token | CVENTSDK_O_AUTH2_AUTHORIZATION_CODE |

You can set the security parameters through the security optional parameter when initializing the SDK client instance. The selected scheme will be used by default to authenticate with the API for all operations that support it. For example:

import { CventSDK } from "@cvent/sdk";

const cventSDK = new CventSDK({
  security: {
    oAuth2ClientCredentials: {
      clientID: process.env["CVENTSDK_CLIENT_ID"] ?? "",
      clientSecret: process.env["CVENTSDK_CLIENT_SECRET"] ?? "",
      tokenURL: process.env["CVENTSDK_TOKEN_URL"] ?? "",
      scopes: process.env["CVENTSDK_SCOPES"] ?? "",
    },
  },
});

async function run() {
  const result = await cventSDK.users.getAccountUserGroups({
    token: "1a2b3c4d5e6f7g8h9i10j11k",
    filter: "name eq 'My User Group'",
  });

  for await (const page of result) {
    console.log(page);
  }
}

run();

Per-Operation Security Schemes

Some operations in this SDK require the security scheme to be specified at the request level. For example:

import { CventSDK } from "@cvent/sdk";

const cventSDK = new CventSDK();

async function run() {
  const result = await cventSDK.authentication.oauth2Token({
    username: "",
    password: "",
  }, {
    grantType: "client_credentials",
    clientId: "djc98u3jiedmi283eu928",
    scope: "event/events:read event/attendees:read",
    redirectUri: "https://example.com/redirect",
    refreshToken: "dn43ud8uj32nk2je",
    code: "AUTHORIZATION_CODE",
  });

  console.log(result);
}

run();

Available Resources and Operations

Appointments

AttendeeActivities

AttendeeInsights

AttendeeMessages

Attendees

AudienceSegments

Authentication

BadgePrintJob

BadgePrinterPools

Budget

Bulk

Campaigns

CardTokens

Compliance

Contacts

CustomFields

Discounts

Emails

EventCredits

EventFeatures

EventRole

EventTravel

Events

EventsPlusHub

Exhibitor

ExhibitorContent

ExhibitorTeam

File

Hooks

Housing

HousingHotels

Leads

MeetingRequest

ProcessForm

ProposalDraft

Seating

Sessions

Signatures

Speakers

Surveys

TravelAccounts

TravelRFPs

TravelSuppliers

Usage

UserSCIM

Users

Video

Webcasts

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.