G2 reviews for a product API reference

A page G2 refuses is a 503 naming the block, never an empty result. The answer carries the product's aggregate rating and its reviews.

Request

POSThttps://api.scrapercompany.com/v1/g2/reviews

Authenticate with your API key in the x-api-key header (see Authentication).

Run this request on your own API key from this page, with the values you type. Signed out? Sign in or get an API key.

Body

JSON object. Unknown fields are rejected with 422.

productstringrequiredmin length 1, max length 120
G2 product slug from its URL.
pageintegerdefault 1min 1, max 500
Review page.

Example request

curl -X POST "https://api.scrapercompany.com/v1/g2/reviews" \
  -H "x-api-key: $SCRAPERCOMPANY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product": "slack"
  }'

Response

200 — One page of G2 reviews. Metered responses carry x-credits-charged and x-credits-remaining headers (see credit headers).

200 response

{
  "search_parameters": {
    "engine": "g2_reviews",
    "product": "slack",
    "page": 1
  },
  "product": {
    "name": "Slack",
    "rating": 4.5,
    "ratings_count": 33100
  },
  "reviews": [
    {
      "source": "g2",
      "rating": 5,
      "title": "Great for teams",
      "text": "Keeps everyone in sync.",
      "date": "2026-09-01",
      "author": "Example Author"
    }
  ],
  "total": 1,
  "meta": {
    "source": "g2",
    "elapsed_s": 0
  }
}

Errors

Errors return a JSON body with a detail field. Failed requests are not charged. See Errors for the full list and retry advice.

Status	Meaning	Retry?
`401`Unauthorized	Missing or invalid API key. `{"detail":"missing or invalid API key"}`	No, fix the request
`402`Payment Required	Not enough credits for this request: the account's credits mode is `enforce` (`mode` in `GET /v1/billing`) and the request costs more than the available credits. Nothing is run or charged. `{"detail":"insufficient credits: this request costs 5, 0 available. Credits renew 2026-11-01."}`	No, fix the request
`422`Unprocessable Content	Request validation failed. `detail` is a list of problems for schema errors, or a string for semantic checks performed by the endpoint. `{"detail":[{"loc":["body","name"],"msg":"Field required","type":"missing"}]}`	No, fix the request
`429`Too Many Requests	Too many requests: the key's requests-per-minute limit was exceeded, or (in `enforce` credits mode) the plan's concurrent-request limit. No rate-limit or Retry-After headers are sent; back off and retry. `{"detail":"rate limit 60/min exceeded"}`	Yes, with backoff
`502`Bad Gateway	The upstream source failed, blocked the request or returned an unusable answer. Safe to retry later; failed requests are not charged. `{"detail":"RuntimeError"}`	Yes, with backoff
`503`Service Unavailable	Temporarily unavailable: a dependency of this endpoint is down, or the upstream source changed its contract. Retry later. `{"detail":"database unavailable: OperationalError"}`	Yes, with backoff

Try it

Press Try it above to run this request on your own key, with the values you type (sign in first). For a no-code walkthrough, use the workspace’s guided Try it.

Export your key: export SCRAPERCOMPANY_API_KEY=sk_... (no key yet? start a free trial).
Copy the cURL example above and run it in a terminal.

Credits

2 credits per successful call (2 per page (an empty page and failed requests are free)). Failed, blocked and empty results are free.

Request#

Body#

Example request#

Response#

Errors#

Try it#