Quora Dataset Builder
Pricing
from $1.00 / 1,000 results
Go to Apify Store
Quora Dataset Builder
Build bounded normalized Quora datasets from public URLs or native search seeds.
Quora Dataset Builder
Pricing
from $1.00 / 1,000 results
Build bounded normalized Quora datasets from public URLs or native search seeds.
Overview is faster; detail follows visible answers, comments, and profile activity.
Terms used to discover public Quora records before joining them.
Choose the public record types to include.
[ "question", "answer", "comment", "profile", "topic", "space", "post"]Choose the dataset layout: normalized rows for databases, nested answers for parent-oriented JSON, flat rows for spreadsheets, or relationship rows for graph tools.
Optional export selection for API users. Leave empty to return every observed buyer-relevant field; fields absent from a page are omitted.
[]Keep a relationship when one endpoint is visible but the other cannot be verified.
Choose the public relationship groups to include. Only relationships explicitly visible on the page are returned.
[]Enable explicitly labeled profile follower/following/followed-question/Space/Topic relationship collections. This does not prove a complete list.
Enable explicitly labeled question follower or want-answer collections. Sensitive identity rows also require the privacy gate.
High-sensitivity opt-in for explicitly labeled answer upvoter identities; requires includeSensitiveRelationshipData=true.
Allow sensitive relationship details when you explicitly request follower, followed-by, want-answers, or voter relationships.
Emit privacy-preserving relationship_collection rows with the real observed total (collection_total_text/collection_total_value) but no target identities. Requires relationship_collection in resultTypes. Observed totals are not always a server-confirmed count.
Enable explicitly labeled Space contributor, moderator, and admin collections.
Retain bounded explicit Space post/question membership edges; this never claims a complete Space inventory.
Bound explicit links emitted from each labeled relationship collection. Zero emits no relationship-collection edges and never means an empty collection.
Maximum question seeds or discovered question pages to process.
Maximum visible answers per question. Use a higher value, up to 50,000, when you want more answers; 0 skips answer rows in detailed mode.
Keep question rows in the joined dataset.
Keep deduplicated author rows supported by visible profile links.
Add a bounded public profile snapshot for each visible author profile link.
Keep Topic records and explicit Topic relationships.
Keep Space records and explicit Space relationships.
Collect visible comments and replies.
Retain links inside an explicitly labeled related/attached region scoped to answer cards; unlabeled navigation and neighboring regions are excluded.
Bound eligible related-content links per answer when enabled; zero emits no related-content items.
Retain only comments with an explicit visible Top/Most helpful/Popular comments label. Unknown comments are excluded and counted; votes and position are not used as top evidence.
Order visible comments by Quora order, upvotes, reactions, replies, or newest date.
Enable bounded visible nested comment replies and explicit parent paths; this also enables comment rows. Hidden or unexpanded replies are not inferred.
Return media URLs visibly attached to records.
Return external links visibly attached to records.
Return explicit links between questions, answers, authors, Topics, Spaces, posts, and comments.
Maximum visible comments per answer. Use 0 to collect every comment Quora exposes before the run limit or access boundary.
Maximum visible nested reply depth when includeReplyGraph is enabled; reaching the bound is not complete history.
Maximum relationship records to return in addition to content rows.
Choose the Quora language version to request when available. This selects page language; it does not translate content.
Public Quora URLs. The actor detects whether each is a question, answer, profile, topic, Space, or post.
Maximum joined records returned across all sources.
Add one clearly labelled row for each page Quora did not make available. Leave off for a clean content-only dataset.
Maximum records collected from each URL or search source before moving to the next source.
Standard is the cost-conscious default. Maximum reach uses stronger routing when available. Direct connection is mainly useful when you already control the connection.