API Reference
Use Crawlora's Capterra API endpoints to extract supported public Capterra data as structured JSON. This documentation covers 3 active endpoints including Get a Capterra product, Get Capterra product reviews, Search Capterra products. Developers can use these endpoints for monitoring, enrichment, research dashboards, internal data pipelines, and agent-native workflows without maintaining platform-specific scraping code. Each endpoint page documents authentication, request parameters such as product_id, q, cURL examples, response examples, response schemas, errors, credit cost, and Playground testing. Send requests to the Crawlora API with an x-api-key header, review usage and plan limits on pricing, and test safe sample requests in Playground before moving the workflow into production.
Choose an endpoint, send an authenticated request with the x-api-key header, and inspect the normalized JSON response. The examples below use the public Crawlora API base URL and the same endpoint catalog used by Playground.
curl -X GET "https://api.crawlora.net/api/v1/capterra/search?q=coffee" \
-H "x-api-key: $CRAWLORA_API_KEY"These endpoint cards are generated from the active Crawlora endpoint catalog, including method, path, auth mode, credit cost, parameter summary, docs, and Playground links.
/capterra/productapiKey2 credits/requestReturns a normalized Capterra product profile: name, description, category, and aggregate rating. Credential-free public Capterra data, rendered from the product page through proxied browser renderers.
Required params: product_id:query
/capterra/product/reviewsapiKey3 credits/requestReturns a page of normalized Capterra reviews (author, headline, rating) plus the product's aggregate rating. Credential-free public Capterra data, rendered from the reviews page through proxied browser renderers.
Required params: product_id:query
/capterra/searchapiKey3 credits/requestReturns Capterra search-result products (id, name, url, description, rating). Credential-free public Capterra data, rendered from the search page through proxied browser renderers. Note: Capterra renders a fallback product list even for queries with no genuine match, rather than a distinct empty-results page, so callers should treat low-relevance results as an upstream characteristic, not a bug.
Required params: q:query
| Endpoint | API path | Method | Credits | Required params | Docs | Playground |
|---|---|---|---|---|---|---|
| Get a Capterra product | /capterra/product | GET | 2 credits/request | product_id:query | View docs | Try endpoint |
| Get Capterra product reviews | /capterra/product/reviews | GET | 3 credits/request | product_id:query | View docs | Try endpoint |
| Search Capterra products | /capterra/search | GET | 3 credits/request | q:query | View docs | Try endpoint |