Jifflenow

Jifflenow is a B2B meeting automation and scheduling platform for trade shows, conferences, and corporate events, now part of Cvent (acquired 2021) as Cvent Jifflenow. It lets sales and event teams request, approve, and confirm meetings before attendees arrive on the show floor, with automated routing and notifications, a unified calendar that combines customer meetings and internal staff activities, on-site mobile check-in and no-show tracking, and reporting dashboards that tie meeting volume and outcomes back to pipeline. It integrates with Salesforce (native CRM sync of accounts, opportunities, campaigns, and leads), Outlook, and iCapture badge scanning. The standalone jifflenow.com now redirects to Cvent, but the Jifflenow REST API remains live and publicly documented on the acquirer's developer portal at developers.cvent.com under its legacy-API section: roughly twenty JSON operations over events, meetings, sessions, meeting types, users, calendar blocks, event topics, badge-scan ingestion, and shared meeting links, served from a per-tenant https://.jifflenow.com/api host and secured with OAuth 2.0 client credentials. No OpenAPI, SDK, webhook surface, or agent surface is published for it.

Jifflenow publishes 1 API on the APIs.io network. Tagged areas include Company, Automation, Event, Meetings, and Scheduling.

Jifflenow’s developer surface includes documentation, API reference, getting-started guide, support, pricing, authentication, sandbox, and 18 more developer resources.

🌐 Visit website 📡 Source on GitHub

32.9/100 thin ▬ flat Agent 8/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Automation Event Meetings Scheduling Event Marketing B2B Sales Trade ShowsMeeting AutomationAppointmentsBadge Scanning

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 32.9/100 · thin

Contract Quality 0.0 / 25

Developer Ergonomics 12.4 / 20

Access Clarity 9.5 / 20

Operational Transparency 2.1 / 13

Contract Governance 2.2 / 12

Discoverability 6.9 / 10

Agent readiness — 8/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/jifflenow: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

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,...

Pricing Plans 1

Published pricing tiers and plan structures.

Jifflenow Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Jifflenow Rate Limits

0 limits

RATE LIMITS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Jifflenow Authentication

oauth2 · 2 schemes

SECURITY

Jifflenow Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Jifflenow Trust Center

SOC 2, ISO 27001, PCI DSS, GDPR, CSA STAR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Jifflenow Scopes

1 scope · clientCredentials

1 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

DataModel

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 5

Authentication, authorization, and security posture

Compliance

TrustCenter

DomainSecurity

Authentication

OAuthScopes

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: jifflenow
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: contact-sales
  onboarding: tenant-admin
  trial: false
  try_now: false
  public: false
  label: Docs public, access sales-gated
  confidence: high
  source:
  - https://developers.cvent.com/docs/legacy-api/jifflenow-api/introduction
  - https://developers.cvent.com/docs/legacy-api/jifflenow-api/getting-started
  - url: https://www.jifflenow.com
    status: 301
    note: declared website redirects to https://www.cvent.com/en/event-marketing-management/cvent-jifflenow — a different
      registrable domain (jifflenow.com -> cvent.com), possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-08-13'
  method: searched
  note: 'The full API reference is publicly readable with no account. Credentials are not: Jifflenow is sold as a Cvent add-on
    license, and a tenant admin with the "Can manage integrations" privilege mints the Client ID/Secret/Subdomain inside the
    product.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/jifflenow.png
name: Jifflenow
description: 'Jifflenow is a B2B meeting automation and scheduling platform for trade shows, conferences, and corporate events,
  now part of Cvent (acquired 2021) as Cvent Jifflenow. It lets sales and event teams request, approve, and confirm meetings
  before attendees arrive on the show floor, with automated routing and notifications, a unified calendar that combines customer
  meetings and internal staff activities, on-site mobile check-in and no-show tracking, and reporting dashboards that tie
  meeting volume and outcomes back to pipeline. It integrates with Salesforce (native CRM sync of accounts, opportunities,
  campaigns, and leads), Outlook, and iCapture badge scanning. The standalone jifflenow.com now redirects to Cvent, but the
  Jifflenow REST API remains live and publicly documented on the acquirer''s developer portal at developers.cvent.com under
  its legacy-API section: roughly twenty JSON operations over events, meetings, sessions, meeting types, users, calendar blocks,
  event topics, badge-scan ingestion, and shared meeting links, served from a per-tenant https://<companyname>.jifflenow.com/api
  host and secured with OAuth 2.0 client credentials. No OpenAPI, SDK, webhook surface, or agent surface is published for
  it.'
url: https://raw.githubusercontent.com/api-evangelist/jifflenow/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- accel
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-13'
tags:
- Company
- Automation
- Event
- Meetings
- Scheduling
- Event Marketing
- B2B
- Sales
- Trade Shows
- Meeting Automation
- Appointments
- Badge Scanning
tags_raw:
- Company
- Automation
- Events
- Meetings
- Scheduling
- Event Marketing
- B2B
- Sales
- Trade Shows
- Meeting Automation
- Appointments
- Badge Scanning
apis:
- 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
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Compliance
  url: https://www.cvent.com/en/trust
- type: TrustCenter
  url: security/jifflenow-trust-center.yml
- type: DomainSecurity
  url: security/jifflenow-domain-security.yml
- type: Website
  url: https://www.jifflenow.com
- type: DeveloperPortal
  url: https://developers.cvent.com/
- 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: Support
  url: https://support.cvent.com/
- type: Pricing
  url: https://www.cvent.com/en/event-management-software/cvent-pricing
- type: TermsOfService
  url: https://www.cvent.com/en/company/legal
- type: PrivacyPolicy
  url: https://www.cvent.com/en/privacy-policy
- type: StatusPage
  url: https://status.cvent.com
- type: Authentication
  url: authentication/jifflenow-authentication.yml
- type: OAuthScopes
  url: scopes/jifflenow-scopes.yml
- type: Conventions
  url: conventions/jifflenow-conventions.yml
- type: ErrorCatalog
  url: errors/jifflenow-problem-types.yml
- type: Lifecycle
  url: lifecycle/jifflenow-lifecycle.yml
- type: DataModel
  url: data-model/jifflenow-data-model.yml
- type: Sandbox
  url: sandbox/jifflenow-sandbox.yml
- type: Conformance
  url: conformance/jifflenow-conformance.yml
- type: Plans
  url: plans/jifflenow-plans-pricing.yml
- type: RateLimits
  url: rate-limits/jifflenow-rate-limits.yml
- type: Packages
  url: packages/jifflenow-packages.yml
- type: LLMsTxt
  url: llms/jifflenow-llms.txt
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 13
  pass: local-v1
  note: Contract discovery beat the redirect. jifflenow.com 302s to Cvent, but the live Jifflenow REST API reference was found
    on the acquirer's portal at developers.cvent.com/docs/legacy-api/jifflenow-api/ by reading the Next.js route manifest;
    20 operation pages were harvested into authentication, scopes, conventions, errors, lifecycle, data-model, sandbox, conformance,
    plans, rate-limits, packages and llms artifacts. No OpenAPI, no .well-known document, no MCP server, no agent card, no
    SDK, no webhooks.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/jifflenow"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/jifflenow/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/jifflenow/evidence"

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.

GitHub Google LinkedIn

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