canonical: https://jentic.com/apis/g2.com/g2-api

# G2 API

Jentic publishes the only available OpenAPI specification for G2 API, keeping it validated and agent-ready. The G2 API exposes G2's software-buyer dataset including products, categories, survey responses, review questions, and answers, plus buyer-intent signals and webhook syndication endpoints. The 23 operations are scoped under /api/v1/* and use a token-based apiKey scheme so partners can pull product profiles, category trees, and aggregated review responses to power competitive intelligence, marketing pages, and buyer-intent enrichment. Outputs include normalised product IDs, category mappings, and structured survey-question responses that can be joined to a CRM record. The API targets revenue, marketing-ops, and product-marketing teams that already license G2 data and need it inside automated workflows rather than the G2 dashboard.

## For AI agents

Pull G2 product profiles, category trees, survey-response data, and buyer-intent signals via token-authenticated REST endpoints scoped under /api/v1/.

## Scope

Does not handle review collection from end users, payment for G2 listings, or social-share rendering - use for partner-token reads of G2 product, review, category, and buyer-intent data only.

## Capabilities

- Look up G2 product profiles and metadata via /api/v1/products and /api/v1/products/{id}
- Retrieve aggregated survey responses for a product through /api/v1/products/{id}/survey-responses
- Browse G2's category taxonomy and individual category records via /api/v1/categories endpoints
- Access review questions and structured answers through /api/v1/questions and the Answers tag
- Subscribe to webhook deliveries for buyer-intent signals via the Webhooks and Buyer Intent tags
- Syndicate G2 review and rating data into partner sites through the Syndication tag operations

## Use cases

### Competitive Intelligence Dashboard

Build a competitive view that pulls G2 product profiles via /api/v1/products and joins their survey-response aggregates so revenue teams can compare positioning, satisfaction scores, and feature ratings against direct competitors. Refresh weekly using the same token-authenticated endpoints rather than scraping g2.com.

Example prompt: Call /api/v1/products with a slug filter for each competitor, then /api/v1/products/{id}/survey-responses for each returned id.

### Buyer-Intent CRM Enrichment

Enrich CRM accounts with G2 buyer-intent signals by subscribing the relevant Webhooks tag operations and writing the events into Salesforce or HubSpot. Sales gets notified when a target account researches the company on G2 and can prioritise outreach without checking a separate portal.

Example prompt: Configure a webhook through the Webhooks operation, then map incoming buyer-intent events into the matching CRM account.

### Review Syndication Page

Power a marketing site's reviews section by calling the Syndication-tagged endpoints to pull approved G2 review answers and survey questions, then render them server-side. The token-authenticated read keeps the data fresh without copy-paste from g2.com.

Example prompt: Call /api/v1/products/{id}/survey-responses and the Answers operation for the company's product and render the responses in the page template.

### Agent-Driven G2 Lookups via Jentic

A revenue-ops agent receives a request like 'pull G2 reviews for ProductName' and uses Jentic to discover the right /api/v1/products endpoint, load its parameter schema, and execute the call against the workspace's G2 token. Jentic isolates the token so the agent never has direct access to it.

Example prompt: Search Jentic for 'list g2 products', load /api/v1/products, and execute it filtered by the product slug from the user's request.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api/v1/products | List G2 products |
| GET | /api/v1/products/{id} | Get a single product by id |
| GET | /api/v1/products/{id}/survey-responses | List survey responses for a product |
| GET | /api/v1/survey-responses | List survey responses |
| GET | /api/v1/categories | Browse the G2 category taxonomy |
| GET | /api/v1/questions | List review questions |

## Key resources

- **Products** — Look up product profiles and metadata under /api/v1/products.
- **Survey Responses** — Retrieve aggregated review responses tied to a product or survey id.
- **Categories** — Browse G2's category taxonomy via /api/v1/categories.
- **Questions** — Access review questions associated with categories or products.
- **Answers** — Retrieve structured answer payloads for review questions.
- **Buyer Intent** — Receive buyer-intent signals about accounts researching the product.
- **Webhooks** — Subscribe to G2 event deliveries.
- **Syndication** — Pull review and rating content approved for off-site display.

## Why Jentic

- **Setup:** Wiring the G2 API by hand means formatting its 'Token token=' Authorization header against data.g2.com and threading your partner token through product, review, category, and buyer-intent reads yourself. Through Jentic you install once, import the G2 API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** G2 puts the product id in the URL path (/api/v1/products/{id}/survey-responses), so a rule can pin your agent to one product: it can read that product and its survey responses and nothing else. You choose the operations it may call, so broad category or question reads are not included unless you add them.
- **Credential handling:** Your G2 partner token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read a G2 product' or 'get survey responses for a product', and Jentic returns the matching G2 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **G2 API (g2-crowd)** — Companion G2 surface scoped under data.g2.com/api/v1 with a smaller endpoint subset.
- **eTrusted (Trusted Shops) API** — Review-collection and trust-mark API that targets buyer reviews from a different reviewer pool than G2.

## FAQ

### Why is there no official OpenAPI spec for G2 API?

G2 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call G2 API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the G2 API use?

G2 uses a token-based apiKey scheme (tokenAuth in the spec) - partners pass their G2-issued token on each request to data.g2.com. Through Jentic, the token is held encrypted in the vault and injected at execution so it never enters the agent's prompt.

### Can I retrieve survey responses for a specific product?

Yes. Call GET /api/v1/products/{id}/survey-responses with the product id you obtained from /api/v1/products and G2 returns the aggregated review responses for that product, suitable for syndication or competitive comparison.

### What are the rate limits for the G2 API?

G2 enforces partner-tier rate limits that are negotiated per contract; the OpenAPI spec does not pin numeric values. Watch for HTTP 429 responses and contact your G2 partner manager for the exact ceiling assigned to your token.

### How do I subscribe to G2 buyer-intent webhooks through Jentic?

Run a Jentic search for 'subscribe to g2 buyer intent webhook', load the matching Webhooks-tag operation, and execute it with your callback URL and product id. Get started with Jentic One, the self-hosted execution layer.

### Can I browse the G2 category taxonomy with this API?

Yes. GET /api/v1/categories returns the category list and GET /api/v1/categories/{id} returns a single category record, allowing you to walk G2's taxonomy and map its node ids to internal category fields.

### Can I limit what my agent is allowed to do with the G2 API?

Yes. Because you run Jentic One yourself, your own rules decide which G2 operations and which partner token the agent may use. The G2 API puts the product id in the URL path, as in GET /api/v1/products/{id}/survey-responses, so you can pin the agent to a single product and let it read only that product and its survey responses. You pick the operations it may call, so broad category or question reads under /api/v1/categories and /api/v1/questions stay out of reach unless you explicitly add them.