/gartner/products

POST /api/gartner/products

Price: 10 credits

Get Gartner Peer Insights (gartner.com) product details by product seoName or full product URL

How to use it

Get full details of a Gartner Peer Insights (gartner.com) enterprise-software product by seoName or product URL. Returns name, vendor, average rating, review count, star-rating distribution, product and pricing description, screenshots, the product's market, and vendor company profile (type, founded year, headquarters, employee range, website).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Gartner Peer Insights product identifier. Accepts a product seoName ('forcepoint-dlp') or full product URL ('https://www.gartner.com/reviews/product/forcepoint-dlp'). (examples: "forcepoint-dlp", "https://www.gartner.com/reviews/product/forcepoint-dlp"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?gartner\.com[^\s]*|[a-z0-9][a-z0-9.-]*)$)

Response

• @type string (default: "GartnerProduct")
• id string required
• alias string required
• name string required
• vendor_id string nullable
• vendor_name string nullable
• vendor_alias string nullable
• image string nullable
• average_rating number nullable
• review_count integer nullable
• rating_distribution object nullable
  • @type string (default: "GartnerRatingDistribution")
  • star_1 integer (default: 0)
  • star_2 integer (default: 0)
  • star_3 integer (default: 0)
  • star_4 integer (default: 0)
  • star_5 integer (default: 0)
• description string nullable
• pricing_description string nullable
• is_service boolean nullable
• is_legacy boolean nullable
• updated_at string nullable
• screenshots array (default: [])
• market object nullable
  • @type string (default: "GartnerProductMarket")
  • id string nullable
  • name string required
  • alias string nullable
  • review_count integer nullable
  • url string nullable
• company object nullable
  • @type string (default: "GartnerProductCompany")
  • name string nullable
  • alias string nullable
  • description string nullable
  • company_type string nullable
  • founded_year integer nullable
  • headquarter_city string nullable
  • headquarter_country string nullable
  • min_employee_range integer nullable
  • max_employee_range integer nullable
  • revenue string nullable
  • website_url string nullable
  • parent_company string nullable
• url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Product not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.