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

# G2 API (g2-crowd)

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.

## For AI agents

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

## Scope

Does not handle buyer-intent webhooks, syndication, or review collection - use for partner-token reads of G2 products, categories, questions, answers, and survey responses only.

## Capabilities

- 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
- Retrieve structured answer payloads through the /answers and `/answers/{id}` endpoints
- Manage resource subscriptions for partner data feeds via the resource-subscriptions tag

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Products** — List and look up G2 product profiles.
- **Survey Responses** — Read aggregated and individual survey responses tied to products.
- **Categories** — Browse the G2 category taxonomy.
- **Questions** — Read review questions used in G2 surveys.
- **Answers** — Read structured answers tied to questions.
- **Resource Subscriptions** — Manage partner data-feed subscriptions.

## Why Jentic

- **Setup:** Wiring the G2 API by hand means formatting its 'Token token=' Authorization header against data.g2.com/api/v1 and threading your partner token through product, category, question, answer, and survey-response 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 (`/products/{id}`), so a rule can pin your agent to one product: it can read that product and nothing else. You choose the operations it may call, so broad category, question, or answer 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 'list survey responses', 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** — Wider G2 partner surface with 23 endpoints including buyer-intent, webhooks, and syndication.
- **eTrusted (Trusted Shops) API** — Review-collection and trust-mark API that surfaces buyer reviews independent of G2's software-buyer graph.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the G2 API (g2-crowd)?

Yes. Because you run Jentic One yourself, your own rules decide which G2 operations and credentials the agent may use. Since G2 puts the product id in the URL path at `/products/{id}`, you can pin the agent to a single product so it reads that product and nothing else. You choose the operations it may call, so broad reads across /categories, /questions, /answers, and /survey-responses are excluded unless you explicitly add them.