Jifflenow · OAuth Scopes

Jifflenow OAuth Scopes

OAuth 2.0 searched

Jifflenow publishes 1 OAuth 2.0 scope via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Jifflenow API on a user’s behalf.

Tokens are issued from https://.jifflenow.com/api/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyAutomationEventMeetingsSchedulingEvent MarketingB2BSalesTrade ShowsMeeting AutomationAppointmentsBadge Scanning

Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://.jifflenow.com/api/oauth/token

Flows
clientCredentials

Scopes (1)

Scope	Description	Flows
public	The scope value shown in the documented sample token response. The docs gloss it as "limited access to public resources". No other scope string appears anywhere in the published reference.	clientCredentials

📄 Provider scope reference: https://developers.cvent.com/docs/legacy-api/jifflenow-api/getting-started

Source

OAuth Scopes

generated: '2026-08-13'
method: searched
source: https://developers.cvent.com/docs/legacy-api/jifflenow-api/getting-started
docs: https://developers.cvent.com/docs/legacy-api/jifflenow-api/getting-started
note: >-
  Jifflenow documents OAuth 2.0 but publishes no scope reference page and no OpenAPI, so there is no
  enumerable scope catalog. Scopes are granted implicitly: at integration setup the tenant admin
  picks which Jifflenow APIs the integration may call and the docs state that this "adds the
  required scopes to your credentials". The only scope value the documentation actually shows is the
  one returned in the sample token response.
schemes:
  - name: OAuth2 Client Credentials
    source: https://developers.cvent.com/docs/legacy-api/jifflenow-api/getting-started
    flows:
      - flow: clientCredentials
        tokenUrl: https://<companyname>.jifflenow.com/api/oauth/token
scopes:
  - scope: public
    description: >-
      The scope value shown in the documented sample token response. The docs gloss it as "limited
      access to public resources". No other scope string appears anywhere in the published reference.
    flows: [clientCredentials]
    sources: [https://developers.cvent.com/docs/legacy-api/jifflenow-api/getting-started]
scope_model:
  enumerable: false
  granted_by: >-
    Per-integration API selection in the Jifflenow admin UI (Settings -> Integrations), not by a
    scope string the client requests.
  reference_page: null

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
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 scope set

curl "https://apis.io/api/v1/scopes/jifflenow-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.

GitHub Google LinkedIn

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