Capterra Reviews API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Read Capterra user reviews of a software product, with pros, cons, scores for ease of use, support, features and value, and reviewer role, industry and company size. Pass the product's /p/ URL in company to avoid name mix-ups; incentivized marks reviews collected with a reward.
Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.
Please help me write a data collection script with the EveryInfra Capterra Reviews endpoint (capterra/reviews).
Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to capterra and action to reviews, and put the parameters inside params.
- Required parameters:
- company: Specifies the Capterra software product name or the full /p/<product_id>/<slug>/ URL. Passing the product URL is recommended to avoid name matching ambiguities.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, url, title, text, pros, cons, rating, rating_scale, ease_of_use_rating, customer_service_rating, features_rating, value_rating; 26 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=capterra.
- Example request body:
{
"platform": "capterra",
"action": "reviews",
"params": {
"company": "<软件产品名称或 Capterra 产品 URL>"
}
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | capterra | Platform identifier, fixed value. |
action | body | string | Yes | reviews | Capability identifier, fixed value. |
company | body.params | Not declared | Yes | - | Specifies the Capterra software product name or the full /p/<product_id>/<slug>/ URL. Passing the product URL is recommended to avoid name matching ambiguities. Refers to a software product, not a legal entity or company website. |
limit | body.params | integer (1–100) | No | 20 | The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "capterra",
"action": "reviews",
"params": {
"company": "<软件产品名称或 Capterra 产品 URL>"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.
{
"id": "req_…",
"platform": "capterra",
"action": "reviews",
"results": [
{
"id": …,
"url": …,
"title": …,
"text": …,
"pros": …,
"cons": …,
"rating": …,
"rating_scale": …,
"ease_of_use_rating": …,
"customer_service_rating": …,
"features_rating": …,
"value_rating": …,
"recommend_rating": …,
"author_name": …,
"author_job_title": …,
"author_industry": …,
"company_size": …,
"usage_duration": …,
"author_verified": …,
"incentivized": …,
"source": …,
"chosen_reasons": …,
"switching_reasons": …,
"vendor_response": …,
"product_url": …,
"posted_at": …,
"platform": …
}
],
"count": …,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
title | Title. null when the platform has no titles (for example text-only posts). |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
pros | Keeps the platform's own meaning |
cons | Keeps the platform's own meaning |
rating | Rating. The scale varies by platform: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards. |
rating_scale | Maximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating. |
ease_of_use_rating | Keeps the platform's own meaning |
customer_service_rating | Keeps the platform's own meaning |
features_rating | Keeps the platform's own meaning |
value_rating | Keeps the platform's own meaning |
recommend_rating | Keeps the platform's own meaning |
author_name | Author's display name. |
author_job_title | Keeps the platform's own meaning |
author_industry | Keeps the platform's own meaning |
company_size | Keeps the platform's own meaning |
usage_duration | Keeps the platform's own meaning |
author_verified | Keeps the platform's own meaning |
incentivized | Keeps the platform's own meaning |
source | Keeps the platform's own meaning |
chosen_reasons | Keeps the platform's own meaning |
switching_reasons | Keeps the platform's own meaning |
vendor_response | Keeps the platform's own meaning |
product_url | Keeps the platform's own meaning |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).
Official references
Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- Capterra: User Reviews, Incentives, and Vendor Responses ↗
Capterra treats reviews as individual user experiences and opinions, and vendor responses do not represent platform endorsement. Reviews submitted via incentive programs are marked with their source. This context explains review backgrounds and does not replace content evaluation based on incentive status.
Checked 2026-09-04