G2 APIs
2 APIs34 Endpoints1 Category
Categories
API Catalog(2 of 2)
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.
23 endpointsG2 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.
11 endpointsConnect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fg2.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fg2.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.