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 is listed with 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.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
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.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/jifflenow/"><img src="https://apis.io/badge/jifflenow/card.svg" alt="Jifflenow on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
10 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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,...
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: