G2 API (g2-crowd)

Name: G2 API (g2-crowd) API
Brand: G2 API (g2-crowd)
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey11 EndpointsREST

For Agents

Read G2 product, category, review-question, and survey-response data through a focused 11-endpoint partner surface authenticated with a TokenAuth header.

Connect the G2 API (g2-crowd) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the G2 API (g2-crowd), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with G2 API (g2-crowd) API.

Look up software product profiles via /products and /products/{id}

Retrieve aggregated survey responses for a product through /survey-responses and /survey-responses/{id}

Browse G2's category taxonomy and individual category records through /categories

Pull review questions linked to categories or products through /questions

GET STARTED

Start building with G2 API (g2-crowd) API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for G2 API (g2-crowd), keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for G2 API (g2-crowd), keeping it validated and agent-ready. This G2 surface is scoped directly under data.g2.com/api/v1 and exposes a tighter set of 11 read endpoints covering products, categories, questions, answers, survey responses, and resource subscriptions. It uses a token-based apiKey scheme (TokenAuth) and is intended for partners who want a focused integration limited to G2's review and category data without the wider syndication, buyer-intent, and webhook surface of the larger G2 API. Responses follow the same product, category, and survey-response shapes as the broader G2 partner API.

Use Cases

Patterns agents use G2 API (g2-crowd) API for, with concrete tasks.

★ Lightweight Review Data Sync

Run a daily job that pulls G2 product, category, and survey-response data into an internal data warehouse using only the read endpoints under data.g2.com/api/v1. The 11-endpoint surface keeps the integration small and audit-friendly compared to the full G2 partner API.

Call /products, then /products/{id} and /survey-responses for each id, and write the rows into the warehouse staging table.

Category Taxonomy Mapping

Map an internal product taxonomy to G2's official category tree by reading /categories and aligning ids so analytics can roll up by canonical category. Mapping makes downstream reports comparable to G2 industry benchmarks.

Call GET /categories and merge the returned category ids onto each product record in the warehouse.

Review Question Audit

Audit which review questions G2 currently asks for a category by reading /questions before launching a new product profile, so marketing knows what attributes will be scored. The endpoint returns the structured question set tied to the category.

Call GET /questions filtered by the category id and return the list of question texts and ids.

Agent-Driven G2 Data Lookup via Jentic

An analytics agent uses Jentic to find the right /products or /survey-responses endpoint based on a natural-language ask, then executes the call against the partner token. Because the surface is small, the agent's tool list stays focused and predictable.

Search Jentic for 'get a g2 product by id', load /products/{id}, and execute it with the id from the user's request.

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for g2 api (g2-crowd), keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/products

List G2 products

GET

/products/{id}

Get a single product by id

GET

/survey-responses

List survey responses

GET

/survey-responses/{id}

Get a single survey response

GET

/categories

Browse categories

GET

/answers

List answers

GET

/questions

List review questions

GET

/products

List G2 products

GET

/products/{id}

Get a single product by id

GET

/survey-responses

List survey responses

GET

/survey-responses/{id}

Get a single survey response

GET

/categories

Browse categories

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

G2 TokenAuth keys are stored encrypted in the Jentic vault (MAXsystem) and injected at execution time, so the agent context never holds the raw token.

Intent-based discovery

Agents search Jentic with intents like 'get a g2 product by id' and Jentic returns /products/{id} along with its id parameter schema, removing the need to read partner documentation.

Time to first call

Direct integration: about 1 week including partner onboarding and warehouse wiring. Through Jentic: under 1 hour to start reading data once the partner token is provisioned.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

G2 API

Wider G2 partner surface with 23 endpoints including buyer-intent, webhooks, and syndication.

Pick this when the workflow needs buyer-intent feeds, webhooks, or syndication beyond the 11 read endpoints in g2-crowd.

Alternative

eTrusted (Trusted Shops) API

Review-collection and trust-mark API that surfaces buyer reviews independent of G2's software-buyer graph.

Choose this when broader review coverage outside G2 is needed or to cross-validate G2 ratings with a different reviewer pool.

FAQs

Specific to using G2 API (g2-crowd) API through Jentic.

Why is there no official OpenAPI spec for G2 API (g2-crowd)?

G2 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call G2 API (g2-crowd) via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the G2 API (g2-crowd) use?

Authentication uses an apiKey scheme named TokenAuth — every request to data.g2.com/api/v1 carries the partner token in the configured header. Through Jentic, the token is held encrypted in the vault so the agent never sees it.

Can I retrieve a single survey response by id?

Yes. GET /survey-responses/{id} returns the structured response body for a single survey-response id, which is useful when you already store G2 ids inside your warehouse and just need a refresh.

What are the rate limits for the G2 API (g2-crowd)?

Rate limits are partner-contract specific and are not embedded in the OpenAPI spec. Watch for HTTP 429 responses and confirm with your G2 partner manager for written numerical ceilings.

How do I sync G2 product data through Jentic?

Run a Jentic search for 'list g2 products', load GET /products, and execute it on a schedule, then call GET /products/{id} for each returned id. Get started at https://app.jentic.com/sign-up.

Does this surface include buyer-intent or webhook endpoints?

No. The g2-crowd surface is intentionally read-only across products, categories, questions, answers, survey responses, and resource subscriptions; for buyer-intent or webhook subscription, use the broader G2 API spec instead.