Jifflenow REST API

The Jifflenow REST API exposes the meeting-automation core of Cvent Jifflenow as JSON over HTTPS. Documented modules cover user management (list users, push users into an event, block a user's calendar), meeting management (meeting entities, meeting-centric and user-centric meeting lists, meeting types, sessions), event management (list, create and update events), badge-scan ingestion from third-party scanners at company and event level, event topics, and shared meeting links for eCampaign events. Operations sit under /api/adapter on a per-tenant subdomain and are scoped to one event by an {event_system_name} path segment. Authentication is OAuth 2.0 client credentials against /api/oauth/token, returning a 30-minute Bearer token. Cvent files it under "Legacy API"; no OpenAPI is published.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/jifflenow-rest-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
name: Jifflenow REST API
description: The Jifflenow REST API exposes the meeting-automation core of Cvent Jifflenow as JSON over
  HTTPS. Documented modules cover user management (list users, push users into an event, block a user's
  calendar), meeting management (meeting entities, meeting-centric and user-centric meeting lists, meeting
  types, sessions), event management (list, create and update events), badge-scan ingestion from third-party
  scanners at company and event level, event topics, and shared meeting links for eCampaign events. Operations
  sit under /api/adapter on a per-tenant subdomain and are scoped to one event by an {event_system_name}
  path segment. Authentication is OAuth 2.0 client credentials against /api/oauth/token, returning a 30-minute
  Bearer token. Cvent files it under "Legacy API"; no OpenAPI is published.
humanURL: https://developers.cvent.com/docs/legacy-api/jifflenow-api/introduction
baseURL: https://<companyname>.jifflenow.com/api
tags:
- Meetings
- Event
- Scheduling
- User
- Sessions
- Badge Scanning
tags_raw:
- Meetings
- Events
- Scheduling
- Users
- Sessions
- Badge Scanning
properties:
- type: Documentation
  url: https://developers.cvent.com/docs/legacy-api/jifflenow-api/introduction
- type: APIReference
  url: https://developers.cvent.com/docs/legacy-api/jifflenow-api/api-request-response
- type: GettingStarted
  url: https://developers.cvent.com/docs/legacy-api/jifflenow-api/getting-started
- type: Authentication
  url: authentication/jifflenow-authentication.yml
- type: OAuthTokenEndpoint
  url: https://<companyname>.jifflenow.com/api/oauth/token
- type: SingleSignOn
  url: https://developers.cvent.com/docs/sso/configuration/jifflenow
- type: SalesforceApp
  url: https://developers.cvent.com/docs/jifflenow-salesforce/setup