/quora/users

POST /api/quora/users

Price: 5 credits

Get Quora user profile by alias or URL

How to use it

Get a Quora user profile by its alias (the /profile/ slug) or full URL. Returns name, headline, bio, image, follower/following counts, answer/question/post counts, content views, Top Writer years, work/education/location credentials, publications the user contributes to, and the Spaces the user administrates or follows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — User profile alias or full Quora profile URL (examples: "Adam-DAngelo"; minLength: 1)

Response

• @type string (default: "QuoraUser")
• id integer nullable
• alias string (default: "")
• name string (default: "")
• image string nullable
• headline string nullable
• bio string nullable
• profile_url string nullable
• is_verified boolean (default: false)
• follower_count integer nullable
• following_count integer nullable
• answer_count integer nullable
• question_count integer nullable
• post_count integer nullable
• view_count integer nullable
• last_month_view_count integer nullable
• award_winning_answer_count integer nullable
• top_writer_years array (default: [])
• top_asker_years array (default: [])
• locations array (default: [])
• publishers array (default: [])
• work array (default: [])
  • @type string (default: "QuoraUserWork")
  • company string (default: "")
  • position string nullable
  • start_year integer nullable
  • end_year integer nullable
• education array (default: [])
  • @type string (default: "QuoraUserEducation")
  • school string (default: "")
  • degree string nullable
  • concentration string nullable
  • start_year integer nullable
  • end_year integer nullable
• spaces array (default: [])
  • @type string (default: "QuoraSpaceRef")
  • id integer nullable
  • name string (default: "")
  • url string nullable
  • item_count integer nullable
  • is_admin boolean (default: false)
• knows_about array (default: [])
  • @type string (default: "QuoraUserExpertise")
  • topic_id integer nullable
  • topic string (default: "")
  • topic_url string nullable
  • answer_count integer nullable
• created_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. Verify the alias or URL. 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.