/freelancer/users/portfolios

POST /api/freelancer/users/portfolios

Price: 5 credits

List the portfolio items a Freelancer.com user published: item title, description, content type, tagged skills with categories, and every attached file with its CDN URL plus the largest available thumbnail and its dimensions.

How to use it

List a Freelancer.com user's portfolio. Pass user (username or numeric id) and count. Each item has id, user_id, item_title, description, content_type, is_featured, skills and files (id, filename, url, thumbnail, width, height), plus modified_at unix seconds. Use the Freelancer user endpoint for the profile itself and the user reviews endpoint for client feedback.

Parameters

• access-token string required

Request body

• timeout 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 (examples: "subhraniljana", "11070607"; minLength: 1)
• count integer required — Max number of portfolio items to return (min: 1)

Response

• @type string (default: "FreelancerPortfolioItem")
• id integer required
• user_id integer nullable
• item_title string nullable
• description string nullable
• content_type string nullable
• is_featured boolean nullable
• skills array (default: [])
  • @type string (default: "FreelancerSkill")
  • id integer required
  • name string nullable
  • alias string nullable
  • category_id integer nullable
  • category_name string nullable
  • is_local boolean nullable
• files array (default: [])
  • @type string (default: "FreelancerPortfolioFile")
  • id integer required
  • filename string nullable
  • url string nullable
  • thumbnail string nullable
  • width integer nullable
  • height integer nullable
• modified_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 — 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.

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.