/trustradius/categories/products

POST /api/trustradius/categories/products

Price: 20 credits

List TrustRadius (trustradius.com) products within a software category by category slug or URL

How to use it

List software products within a TrustRadius (trustradius.com) category by category slug or URL. Returns each product's name, alias, vendor, trust score, rating and review counts, starting price, top-rated flag, pros/cons, and canonical URL. Use trustradius/products for full product detail.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — TrustRadius category identifier. Accepts a category slug ('crm') or a full category URL ('https://www.trustradius.com/categories/crm'). (examples: "crm", "marketing-automation", "https://www.trustradius.com/categories/crm"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?trustradius\.com[^\s]*|[A-Za-z0-9][A-Za-z0-9-]*)$)
• count integer required — Max number of products to return (min: 1)

Response

• @type string (default: "TrustradiusCategoryProduct")
• id string required
• alias string required
• name string required
• short_name string nullable
• image string nullable
• description string nullable
• vendor_name string nullable
• vendor_id string nullable
• website_url string nullable
• score number nullable
• rating_count integer nullable
• review_count integer nullable
• starting_price string nullable
• pricing_url string nullable
• is_top_rated boolean nullable
• is_trial_available boolean nullable
• pros array (default: [])
• cons array (default: [])
• url string required
• position integer required

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 — Category 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.