Skip to content

Tumblr Scraper API for Login-Walled and Lazy-Loaded Feeds

Tumblr pages often sit behind login walls and load comments and post bodies lazily, which makes a plain HTTP fetch return little of value.

OUTPUT FORMATSHTMLJSONMarkdown

A hosted scraping API handles the browser, proxy rotation and anti-bot work so a single request can return the post and blog fields you actually need. This page explains what such an API returns, which request controls change its behaviour, and how to choose the right plan for a Tumblr data project.

What a Tumblr scraping request can return

A single request against a Tumblr blog or post page can return the post title, body text, tags, reblog counts, note totals, blog handle, theme metadata and posting timestamp. Those fields cover the three workflows Tumblr data most often feeds: mapping trending fandoms and topic clusters from tags, comparing follower and reblog activity per post for creator research, and cataloguing blog theme metadata, custom URL handles and descriptions for indie-web mapping. Because the renderer executes the page in a real browser, content that only appears after JavaScript runs is available in the response rather than missing from it.

Field and control map

Use this map to decide which request controls your Tumblr job needs before you write the first call.

Telling three failure modes apart

A Tumblr job that returns thin or empty data usually has one of three causes, and each has a different fix. If the response is a block page or a CAPTCHA, the request looked like a bot: enable stealth_proxy so it routes through residential proxies with a real headless browser. If the response contains the page shell but not the post body or comment section, JavaScript has not run: pass render_js=true and the page is executed server-side before the HTML is returned. If the content is present but differs from what you expect, the page may vary by geography: pass country_code to route through a residential IP in that country. Concurrency limits are a separate concern from these three; they are set per plan rather than per target, so if Tumblr throttles aggressive patterns, space requests out or use multiple sessions.

A worked example: one blog post, one JSON object

Suppose you want to track a single Tumblr post over time. You send its URL with render_js=true so the lazy-loaded comment section is present, then ask for the fields you care about. With extract_rules you map CSS selectors to field names; with ai_extract_rules you describe the fields in natural language and skip selectors entirely. Either way the response arrives as parsed JSON. A realistic target object for one post contains: post title, body text, tags (as a list), reblog count, note total, blog handle, theme metadata and posting timestamp. Store the timestamp alongside the note total and you have a time series you can compare later without re-scraping the same page twice.

How a Tumblr scrape runs end to end

The workflow has four steps. First, create an account to get an API key and starting credits. Second, install a client library for your stack — Python, Node, Go, PHP or Ruby — so each scrape becomes a single function call instead of a browser and proxy stack you maintain yourself. Third, send the Tumblr URL with your API key; the renderer executes the page in a real browser, rotates the IP and returns a response your scraper can act on. Fourth, add advanced parameters only when the page needs them: render_js for JavaScript, stealth_proxy for CAPTCHAs, country_code for geo-targeting and ai_extract_rules for natural-language extraction. Code samples exist for Python, Node.js, Ruby, PHP, Go and cURL, and the dashboard includes a request builder for testing without writing code.

Capabilities beyond a raw HTML fetch

Several optional features extend the basic Tumblr request. AI-powered extraction accepts a natural-language spec and returns structured JSON without selectors. Screenshot capture gives you a visual record of a page for verification. JavaScript scenarios let you click, scroll, wait for dynamic content or run custom code so the scrape simulates real user behaviour. Markdown output turns Tumblr posts into clean text ready for an LLM to analyse for content trends or creator research. And n8n automation lets you run blog-monitoring workflows without writing scraper code.

Reliability, scale and compliance notes

Proxy rotation avoids IP-based blocking, and headless browser rendering mimics real user browsing to lower blocking risk further. The platform is built to scale across thousands of headless browsers and rotating proxies so performance holds during traffic spikes. Typical responses arrive in one to five seconds across most sites, including JavaScript-heavy ones. On data handling, the service does not collect or store personal data from scraped sites unless the user explicitly requests it. Treat these as the vendor's stated operating characteristics and confirm current terms before relying on them for a compliance decision.

Choosing a plan for a Tumblr project

Plan tiers differ on four axes that matter for Tumblr work: monthly API credits, concurrent requests, support level and team features. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included from the entry tier upward. Priority email support, a dedicated account manager and team management appear only at the Business tier and above. Credits are valid for one month and do not roll over, and requests start at one credit each; enabling JS rendering costs five credits per successful request, while premium proxies cost ten or twenty-five depending on whether JS rendering is also on. Use the plan table below to match credit volume and concurrency to your expected page count, and check the current pricing page before purchase since tiers and allowances can change.

Tumblr scraping questions

The answers below cover blocking, no-code use, JavaScript handling, geo-targeting, rate limits and structured JSON output.

Tumblr data field to request control map
Tumblr data fieldHow it is returnedControl to set
Post title, body text, tags, reblog counts, note totals, blog handle, theme metadata, posting timestampParsed JSONextract_rules with CSS selectors, or ai_extract_rules with a natural-language spec
Lazy-loaded comment sections and JS-rendered post bodiesPost-render HTMLrender_js=true
Content that varies by countryResponse from a residential IP in that countrycountry_code
Block pages or CAPTCHAsNormal-looking traffic via residential proxiesstealth_proxy
Visual record of a pageFull-page screenshotScreenshot and extraction rules feature
Clean text for LLM analysisMarkdownMarkdown output feature

Controls and outputs reflect the vendor's documented request parameters; confirm current parameter names and behaviour in the documentation before building.

Plan tiers at a glance (captured reference, subject to change)
PlanMonthly priceAPI creditsConcurrent requestsPriority support, account manager, team management
Hobby$19 /mo75,00025Not included
Freelance$49 /mo250,00050Not included
Startup (Recommended)$99 /mo1,000,000100Not included
Business$249 /mo3,000,000200Included
Business +$599 /mo8,000,000400Included
Enterprise 14$999 /mo14,000,000500Included
Enterprise 24$1,599 /mo24,000,000600Included
Enterprise 41 (Recommended)$2,399 /mo41,000,000700Included
Enterprise 69$3,599 /mo69,000,000800Included
Enterprise 120$5,799 /mo120,000,000900Included

All prices are exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included on every tier. Credits are valid for one month and do not roll over; requests start at one credit each, JS rendering costs five credits per successful request, and premium proxies cost ten or twenty-five credits depending on whether JS rendering is enabled. This is a captured reference; confirm current pricing and allowances before purchase.

Frequently asked questions

Will I get blocked when scraping Tumblr?

The service rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.

Can I scrape Tumblr without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL.

How do I handle JavaScript when scraping Tumblr?

Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.

Can I scrape Tumblr from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country, which is useful when content varies by geography.

What's the rate limit for scraping Tumblr?

The API has concurrency limits per plan rather than per-target rate limits. If Tumblr throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Tumblr?

Two routes produce parsed JSON. With extract_rules you attach CSS selectors to the field names you want. With ai_extract_rules you describe those fields in plain language and skip selectors. Either way, the parsed JSON comes back in the response.

Which Tumblr fields can I extract in one request?

Post title, body text, tags, reblog counts, note totals, blog handle, theme metadata and posting timestamp can all be returned from a single request against a blog or post page.

How do I tell a block apart from missing JavaScript?

A block page or CAPTCHA means the request looked like a bot; enable stealth_proxy. A page shell without the post body or comments means JavaScript did not run; pass render_js=true. Content that is present but differs from expectations may be geo-variant; pass country_code.