Social discussions
Quora API
Retrieve public Quora questions with their embedded answers, single answers, profiles, topics and spaces as structured JSON, and discover questions, answers, posts, profiles, spaces and topics by keyword through a web search index.
Read Quora questions, answers, spaces, profiles and topics, and discover public pages with keyword search.
API availability: Coming soon
http://localhost:3034Public API: https://api.scrapeatlas.com.Endpoints
/v1/quora/questionGet a Quora question with its answers
Read a public Quora question with identity, counts, topics, flags, answers in ranking order, related questions and an indicator of further answers.
Reference/v1/quora/answerGet a Quora answer
Read one public answer page (/{question}/answer/{author} or /{question}/answers/{id}): full rich-text content with images and links, author, credential, timestamps and counters. The answer's identity is verified against the request.
Reference/v1/quora/profileGet a Quora profile
Read a public Quora profile page: identity, verified badge, credential line, description, follower and content counters, account creation time, Top Writer years, employment, education, location and language credentials, expertise topics, spaces the user contributes to and the recent activity Quora embeds in the document.
Reference/v1/quora/topicGet a Quora topic
Read a public Quora topic page: name, follower count, photo, lock and adult flags, related topics and the most viewed writers Quora lists for the topic.
Reference/v1/quora/spaceGet a Quora space
Read a public Quora space home page ({handle}.quora.com): identity, description, follower and member counts, item count, icon, cover, brand colour, the listed contributors and the recent items Quora embeds in the document.
Reference/v1/quora/searchSearch Quora questions
Search public Quora questions by keyword, with titles, snippets and page dates. Pass a result URL to the question endpoint for the full record.
Reference/v1/quora/answersSearch Quora answers
Search public Quora answers by keyword and return answer records in ranking order.
Reference/v1/quora/postsSearch Quora space posts
Search public Quora space posts by keyword, with titles, snippets and page dates.
Reference/v1/quora/profilesSearch Quora profiles
Search public Quora profiles by keyword, with titles, snippets and page dates. Pass a result URL to the profile endpoint for the full record.
Reference/v1/quora/spacesSearch Quora spaces
Search public Quora spaces by keyword and retrieve their space records.
Reference/v1/quora/topicsSearch Quora topics
Search public Quora topics by keyword, with titles, snippets and page dates. Pass a result URL to the topic endpoint for the full record.
ReferenceQuick start
Create an API key on your account page, then call the public API. Values below are placeholders.
curl "https://api.scrapeatlas.com/v1/quora/question?url=https%3A%2F%2Fwww.quora.com%2FWhat-is-an-example-question" \
-H "x-api-key: YOUR_API_KEY"Coverage & limits
- Independent worker on port 3034, QUORA_API_KEY in x-api-key. No login, persistent cookies, proxy, storage, media download or product dependencies.
- Two concurrent operations, 30-second total deadline, at most four Quora document reads per operation (the requested page, up to two canonical redirect hops and one transient retry). Challenges, rate limits and 4xx answers are never retried.
- Keyword search uses the configured search key (QUORA_SEARCH_API_KEY, Brave Search API); the six search routes report search_unavailable without one. One index request per search (20 URLs requested, up to 10 returned after classification and deduplication), 1 MiB index response, recency windows all/hour/day/week/month/year with hour applied at day granularity, ranked by the index. The question, post, profile and topic searches return index metadata; the answers and spaces searches additionally read up to five discovered question or space pages each (a twelve-document budget for the operation).
- Each read drives a fresh headed Patchright Chromium purely as the network stack: JavaScript is disabled, only Quora documents on www.quora.com or the requested space subdomain may leave the process, every subresource and third party is refused, and the document is taken from the network before rendering. Cloudflare's interstitial fails as upstream_challenged. Linux requires Xvfb; readiness checks the browser binary and display.
- 3 MiB decoded HTML per operation, at most 200 embedded Relay payloads of 1 MiB each; 20 answers, 30 related questions, 50 topics, 20 credentials per kind, 20 expertise topics, 20 spaces, 20 feed items, 20 top writers, 50 contributors, 50 images and 100 links per rich-text document.
- Each page embeds its first answers, feed items, expertise topics and spaces; those caps are reported as answers_truncated, activity_truncated, items_truncated, expertise_topics_truncated and spaces_truncated with status partial.
- Identities are verified against the request (slug, handle, topic slug, space host); mismatches fail unsupported_page. Same-platform redirects are followed only between a question's plain and /unanswered/ forms, to a profile's or topic's canonical casing, from the /q/ alias to the space subdomain, and to Quora's own not-found fallbacks.
| HTTP | failure.code | Meaning |
|---|---|---|
| 400 | invalid_request | Missing, duplicate, ambiguous or unsupported parameters, unsupported URL forms, locale mirrors or reserved names. |
| 503 | search_unavailable | The search routes were called without a configured search key. |
| 502 | search_failed | The web search index answered with an error, a non-JSON body or an unexpected shape. |
| 401 | unauthorized | Invalid API key. |
| 404 | not_found | Unknown question, answer, profile, topic or space (Quora's 404 page or its home-page fallback). |
| 429 | upstream_rate_limited | Quora rate limited the request. |
| 502 | upstream_challenged | Quora's Cloudflare edge answered a challenge instead of the document (status challenged). |
| 502 | unsafe_redirect | Quora redirected outside the requested resource (another question, a locale mirror, a login wall). |
| 502 | unsupported_page | Layout, identity or embedded-data checks failed, or a non-HTML document was served. |
| 502 | response_too_large | The page exceeded 3 MiB. |
| 502 | payload_too_complex | The page embedded more or larger Relay payloads than supported. |
| 502 | request_limit | The upstream document budget was exhausted. |
| 502 | upstream_error | Network failure or an unexpected upstream status after one retry. |
| 503 | busy | Both retrieval slots are occupied. |
| 504 | timeout | The 30-second deadline elapsed. |
