G2 · OAuth Scopes

G2 OAuth Scopes

OAuth 2.0 searched

G2 publishes 18 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the G2 API on a user’s behalf.

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.

B2BSoftware DiscoverySoftware ReviewsBuyer IntentMarket IntelligenceProduct CatalogCompetitive IntelligenceReviewsData SolutionsMCP
Scopes: 18 Flows: Method: searched

Scopes (18)

ScopeDescriptionFlows
openid OpenID Connect default scope. Required for OAuth authentication.
profile Profile information on the current user. Required for OAuth authentication.
products.read Read product catalog data.
products.reviews.read Read product reviews.
vendors.read Read vendor data.
buyer_intent.read Read buyer intent signals.
research_boards.read Read research boards.
research_boards.write Create, update, and delete research boards.
data_subscriptions.read Read Data Subscription records.
data_subscriptions.read_write Modify Data Subscription records.
data_subscriptions.write Write Data Subscription records.
performance_analytics.read Read Performance Analytics data.
partner:partner-id.read Access records created in the Partner realm.
g2_activate.read Read G2 Activate locked/unlocked company records.
g2_activate.write Spend credits to unlock G2 Activate companies.
snippets Access review snippets.
openid_admin Administrative OpenID scope.
profile_admin Administrative profile scope.

Source

OAuth Scopes

Raw ↑
generated: '2026-08-29'
method: searched
source: >-
  openapi/g2-api-v2-openapi.yaml (components.securitySchemes.G2OAuth.flows.authorizationCode.scopes
  and per-operation security requirements), enriched from
  https://documentation.g2.com/docs/g2-mcp-server and
  https://documentation.g2.com/docs/developer-portal
docs: https://documentation.g2.com/docs/g2-mcp-server#connect-directly-to-the-g2-mcp-server
provider: G2
providerId: g2
note: >-
  G2 publishes NO single consolidated scopes reference. Two partial lists exist and they do
  not agree: the OpenAPI securityScheme declares six scopes, while the MCP documentation's
  scope table names eight, four of which (products.read, products.reviews.read, vendors.read,
  buyer_intent.read, research_boards.read/write) never appear in the securityScheme. A third
  set is only discoverable from per-operation 403 error titles in the spec
  (performance_analytics.read, g2_activate.read, g2_activate.write) and from operation
  descriptions ("Requires `products.read` scope"). This file is the union, with the source of
  each scope recorded — that divergence is itself the finding.
schemes:
  - name: G2OAuth
    type: oauth2
    flow: authorizationCode
    pkce: S256
    authorizationUrl: https://www.g2.com/oauth/authorize
    tokenUrl: https://www.g2.com/oauth/token
    dynamic_client_registration: false
    registration: https://my.g2.com/developers
  - name: AccountAPIToken
    type: http
    scheme: bearer
    note: >-
      Account tokens are not scoped by OAuth scope strings. They carry a per-endpoint
      Access permission grid selected at token creation in the Developer Portal.
scopes:
  - scope: openid
    description: OpenID Connect default scope. Required for OAuth authentication.
    required: true
    sources: [openapi, mcp-docs, openid-configuration]
  - scope: profile
    description: Profile information on the current user. Required for OAuth authentication.
    required: true
    sources: [openapi, mcp-docs, openid-configuration]
  - scope: products.read
    description: Read product catalog data.
    sources: [mcp-docs, openapi-operation-descriptions]
    note: Named in operation descriptions ("Requires `products.read` scope") but absent from the securityScheme scope map.
  - scope: products.reviews.read
    description: Read product reviews.
    sources: [mcp-docs]
  - scope: vendors.read
    description: Read vendor data.
    sources: [mcp-docs]
  - scope: buyer_intent.read
    description: Read buyer intent signals.
    sources: [mcp-docs]
  - scope: research_boards.read
    description: Read research boards.
    sources: [mcp-docs]
  - scope: research_boards.write
    description: Create, update, and delete research boards.
    sources: [mcp-docs]
    write: true
  - scope: data_subscriptions.read
    description: Read Data Subscription records.
    sources: [openapi]
  - scope: data_subscriptions.read_write
    description: Modify Data Subscription records.
    sources: [openapi]
    write: true
  - scope: data_subscriptions.write
    description: Write Data Subscription records.
    sources: [openapi]
    write: true
    note: Appears in per-operation security requirements but not in the securityScheme scope map.
  - scope: performance_analytics.read
    description: Read Performance Analytics data.
    sources: [openapi]
    note: Enforced with the 403 title "Missing performance_analytics.read scope" on 5 operations.
  - scope: 'partner:partner-id.read'
    description: Access records created in the Partner realm.
    sources: [openapi]
    note: Templated — substitute the caller's partner id.
  - scope: g2_activate.read
    description: Read G2 Activate locked/unlocked company records.
    sources: [openapi-operation-security, openapi-error-titles]
    note: Enforced with the 403 title "Missing g2_activate.read scope".
  - scope: g2_activate.write
    description: Spend credits to unlock G2 Activate companies.
    sources: [openapi-operation-security, openapi-error-titles]
    write: true
    billable: true
    note: >-
      The only scope in the contract that authorizes spending money. Enforced with the 403
      title "Missing g2_activate.write scope".
  - scope: snippets
    description: Access review snippets.
    sources: [openapi]
  - scope: openid_admin
    description: Administrative OpenID scope.
    sources: [openid-configuration]
  - scope: profile_admin
    description: Administrative profile scope.
    sources: [openid-configuration]
scope_count: 18
operational_notes:
  - >-
    Requested scopes must match the Read/Write Permissions enabled on the OAuth app in the
    Developer Portal, or the token request fails with "requested scope is invalid, unknown, or
    malformed". G2's documented remedy is to add scopes back one at a time.
  - Request only the scopes an application requires; permissions are selected per endpoint at app registration.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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/g2-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.

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