What is bulk social data?
Bulk social data is high-volume public social lookup: thousands of handles, posts, or transcripts through the same API you use for a single call. On Social Fetch that still means REST, credits, and the { data, meta } envelope, not a separate dump format.
How teams run bulk on Social Fetch
Fan out concurrent GETs, check balance before large jobs, and log meta.requestId per call. Paid metered routes have no enforced RPS cap; stay under about 500 concurrent requests for reliability. Watch 402 for empty credits and documented lookupStatus for private or missing targets.
Product overview: /bulk-social-data. Catalog: 17 platforms, 137 marketplace operations.
Credits and job design
Budget spend before concurrency. List and search routes can cost more than a single profile GET; some LinkedIn and transcript options document attempt fees or surcharges. Reconcile against meta.creditsCharged, not a spreadsheet guess.
Prefer typed paths once the workflow is fixed. Ask is for routing unknown questions, not nightly fan-out. See /docs/credits for 402 handling and /glossary/rate-limits for throughput notes.
What it is not
It is not a nightly CSV drop of the whole network. You request the entities you need. If you need open-web crawl of arbitrary URLs, that is a different category (see compare pages for Firecrawl and similar).
FAQ
Do bulk jobs get a discount?
Pricing is credit-based. Higher volume usually means buying larger packs or a subscription for included credits, see /pricing and /docs/credits.
Should I use Ask for bulk?
No. Ask is for routing unknown questions. Bulk pipelines should call typed paths.
Where is reliability documented?
/reliability covers live fetch posture and support via requestId.