/freelancer/contests/entries

POST /api/freelancer/contests/entries

Price: 5 credits

List the entries freelancers submitted to a Freelancer.com contest: entry number, title, description, status, contest-holder rating, like count, sell price, every uploaded file with its CDN URL and thumbnail, submission and win timestamps, and the submitting freelancer's public profile.

How to use it

List submissions to a Freelancer.com contest. Pass contest (numeric id, slug or URL) and count; optionally statuses (active/won/withdrawn/eliminated/draft/pending/bought) and sort (time_entered/rating/number). Each item has id, contest_id, number, entry_title, description, status, rating, like_count, sell_price, entry_url, files (url + thumbnail), owner (the freelancer who submitted it) and entered_at/won_at/eliminated_at unix seconds. Get the contest itself from the Freelancer contest endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• contest string required — Contest id, SEO slug or a full contest URL (examples: "2766954", "https://www.freelancer.com/contest/-TechAI-Images-Fast-2766954.html"; minLength: 1)
• statuses array nullable — Keep only entries in these states (one of: "active", "won", "withdrawn", "eliminated", "draft", "pending", "bought")
• sort string nullable — Ordering of the result list (one of: "time_entered", "rating", "number")
• count integer required — Max number of entries to return (min: 1)

Response

• @type string (default: "FreelancerContestEntry")
• id integer required
• contest_id integer nullable
• number integer nullable
• entry_title string nullable
• description string nullable
• status string nullable
• rating number nullable
• like_count integer nullable
• sell_price number nullable
• entry_url string nullable
• files array (default: [])
  • @type string (default: "FreelancerContestEntryFile")
  • id integer required
  • name string nullable
  • url string nullable
  • thumbnail string nullable
• owner object nullable
  • @type string (default: "FreelancerUserBrief")
  • id integer required
  • alias string nullable
  • display_name string nullable
  • tagline string nullable
  • role string nullable
  • company string nullable
  • image string nullable
  • hourly_rate number nullable
  • location object nullable
    • @type string (default: "FreelancerLocation")
    • country string nullable
    • country_code string nullable
    • city string nullable
    • administrative_area string nullable
    • postal_code string nullable
    • latitude number nullable
    • longitude number nullable
  • verification object nullable
    • @type string (default: "FreelancerVerification")
    • is_payment_verified boolean nullable
    • is_email_verified boolean nullable
    • is_phone_verified boolean nullable
    • is_identity_verified boolean nullable
    • is_deposit_made boolean nullable
    • is_profile_complete boolean nullable
    • is_facebook_connected boolean nullable
    • is_linkedin_connected boolean nullable
    • is_freelancer_verified boolean nullable
  • profile_url string nullable
  • registered_at integer nullable
  • is_limited_account boolean nullable
  • is_closed boolean nullable
• entered_at integer nullable
• won_at integer nullable
• eliminated_at integer 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 — The entity was not found, or a precondition failed 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.