POST /api/freelancer/users/reviews
Price: 10 credits
List the reviews a Freelancer.com user received, as a freelancer or as an employer. Every review carries the star rating, free-text feedback, the per-category breakdown (quality, communication, expertise, professionalism, hire-again — or clarity, payment promptness and work-again for employer reviews), on-time and on-budget flags, the bid and actually paid amount with currency, the project or contest it belongs to, and the reviewer's profile.
List reviews received by a Freelancer.com user. Pass user (username or numeric id), count, and role — freelancer for reviews of their delivered work, employer for reviews of them as a client. Optionally filter review_types to project or contest. Each item has id, text, rating, category_ratings, on_time, on_budget, bid_amount, paid_amount and price_usd with currency, context_name/context_url of the project or contest, from_user (the reviewer, with country and profile URL) and submitted_at unix seconds. paid_amount is what the client actually paid, which can differ from the winning bid.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)user string required — Username, numeric user id or a full profile URL of the reviewed user (examples: "subhraniljana", "11070607"; minLength: 1)role string — Whether to return reviews the user received as a freelancer or as an employer (default: "freelancer"; one of: "freelancer", "employer")review_types array nullable — Keep only reviews left for projects or for contests (one of: "project", "contest")count integer required — Max number of reviews to return (min: 1)@type string (default: "FreelancerReview")id integer requiredtext string nullablerating number nullablerole string nullablestatus string nullablecategory_ratings object nullable@type string (default: "FreelancerReviewRatings")quality number nullablecommunication number nullableexpertise number nullableprofessionalism number nullablehire_again number nullableclarity_spec number nullablepayment_prom number nullablework_for_again number nullableon_time string nullableon_budget string nullablecurrency object nullable@type string (default: "FreelancerCurrency")code string nullablesign string nullablename string nullablecountry string nullableexchange_rate number nullablebid_amount number nullablepaid_amount number nullableprice_usd number nullableis_sealed boolean nullablereview_type string nullablecontext_id integer nullablecontext_name string nullablecontext_url string nullableproject_id integer nullableproject_status string nullablefrom_user object nullable@type string (default: "FreelancerUserBrief")id integer requiredalias string nullabledisplay_name string nullabletagline string nullablerole string nullablecompany string nullableimage string nullablehourly_rate number nullablelocation object nullable@type string (default: "FreelancerLocation")country string nullablecountry_code string nullablecity string nullableadministrative_area string nullablepostal_code string nullablelatitude number nullablelongitude number nullableverification object nullable@type string (default: "FreelancerVerification")is_payment_verified boolean nullableis_email_verified boolean nullableis_phone_verified boolean nullableis_identity_verified boolean nullableis_deposit_made boolean nullableis_profile_complete boolean nullableis_facebook_connected boolean nullableis_linkedin_connected boolean nullableis_freelancer_verified boolean nullableprofile_url string nullableregistered_at integer nullableis_limited_account boolean nullableis_closed boolean nullablesubmitted_at integer nullable422 — 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 — User 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.