G2 User Management API Guide

Auth method: API Token (Bearer token in Authorization header)

Setup steps

1. Log in to your G2 seller account at sell.g2.com.
2. Navigate to Settings > API Keys (availability depends on plan).
3. Generate an API token.
4. Pass the token as a Bearer token: Authorization: Token token=

User object field mapping is not yet verified for this app.

List Reviews

• Method: GET
• URL: https://data.g2.com/api/v1/reviews
• Watch out for: This endpoint returns review data, not user/seat management data. No user provisioning endpoint exists in the public API.

Request example

GET /api/v1/reviews?filter[product_id]=<id>&page[size]=25
Authorization: Token token=<YOUR_API_TOKEN>

Response example

{
  "data": [{"id":"...","type":"reviews","attributes":{...}}],
  "meta":{"total_count":120}
}

• Rate limits: G2 public API rate limits are not publicly documented in detail. Limits are enforced per API token.

• Rate-limit headers: Unknown

• Retry-After header: Unknown

• Rate-limit notes: No official rate limit figures published. Contact G2 support for plan-specific limits.

• Pagination method: offset

• Default page size: 25

• Max page size: 100

• Pagination pointer: page[size] / page[number]

• Webhooks available: No

• Webhook notes: G2 does not publicly document webhook support for user management or seller platform events.

• Alternative event strategy: Poll the G2 API for review and product data changes. For user provisioning, manage seats manually via the G2 seller admin UI.

• SCIM available: No
• SCIM version: Not documented
• Plan required: Enterprise
• Endpoint: Not documented

Limitations:

• SCIM provisioning for the G2 seller platform is not publicly documented.
• SSO (SAML) is supported via Okta, Entra ID, and OneLogin for Enterprise plans, but SCIM auto-provisioning availability is unconfirmed in public documentation.
• Contact G2 Enterprise sales for current SCIM support status.

The primary documented API use case is fetching product reviews: GET https://data.g2.com/api/v1/reviews?filter[product_id]=&page[size]=25 with a Bearer token, paginating via page[number] until meta.total_count is exhausted. This is the extent of what the public API reliably supports.

Adding a seller platform admin user has no API equivalent - it requires logging into sell.g2.com, navigating to Settings > Team Members, and sending an email invitation. The Professional plan hard-caps this at 10 total admin users; Enterprise removes that limit.

Configuring SSO for Enterprise plans involves exchanging SAML metadata between G2 seller settings and your IdP (Okta, Entra ID, or OneLogin). SCIM auto-provisioning is not confirmed in any public documentation - do not architect a provisioning workflow around SCIM availability without explicit written confirmation from G2.

Fetch product reviews via API

1. Obtain an API token from G2 seller settings.
2. GET https://data.g2.com/api/v1/reviews?filter[product_id]=&page[size]=25 with Authorization: Token token=.
3. Paginate using page[number] until meta.total_count is exhausted.

Watch out for: This is the primary documented use case for the G2 API. User management is not available via API.

Add a seller platform admin user (manual)

1. Log in to sell.g2.com as an existing admin.
2. Navigate to Settings > Team Members.
3. Invite the new user by email and assign a role.
4. User receives an email invitation to accept access.

Watch out for: No API endpoint exists for this operation. Professional plan limits total admin users to 10; Enterprise allows unlimited admins.

Configure SSO for seller platform (Enterprise)

1. Confirm Enterprise plan with G2 account team.
2. Obtain SAML metadata from G2 seller settings (Settings > SSO).
3. Configure SAML application in your IdP (Okta, Entra ID, or OneLogin).
4. Upload IdP metadata back to G2 seller SSO settings.
5. Test SSO login; SCIM provisioning availability must be confirmed directly with G2 support.

Watch out for: SCIM auto-provisioning is not confirmed in public documentation. Do not assume SCIM is available without explicit confirmation from G2.

The core trap with G2's API is scope mismatch: the API is a review data pipeline, not an identity or access management surface. Developers expecting to automate user lifecycle operations - provisioning, deprovisioning, role changes - will find no endpoints to call.

Every identity operation falls back to manual UI steps, which breaks any automated offboarding or joiner/mover/leaver workflow.

SCIM is the second trap. SSO via SAML is available at Enterprise, but SCIM provisioning is unconfirmed in public documentation. Assuming SCIM parity with other Enterprise SaaS tools will produce a broken integration.

The absence of webhooks compounds this: there is no event-driven path to detect seller platform changes, so polling the review API is the only programmatic option - and it returns no identity data.

API token access itself may be plan-gated, and no official rate limit figures are published. Any integration that depends on sustained API throughput should validate limits directly with the G2 account team before building.