Tumblr Tag Posts Scraper
Pricing
from $1.00 / 1,000 results
Go to Apify Store
Tumblr Tag Posts Scraper
Extract public Tumblr posts from tag feeds with text, media, tags, reblog trails and engagement counts.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer
ScrapingMonkey
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Collect public posts from a specific Tumblr tag feed. Tumblr Tag Posts Scraper saves individual posts with text, tags, media references, dates, visible engagement and author or reblog context.
Start from a known topic tag and build a source-linked content sample for editorial research or media discovery.
| At a glance | Details |
|---|---|
| 📥 Input | Tumblr tag names, hashtags or public tumblr.com/tagged URLs. |
| 📤 Output | One post per success row, with source input retained |
| 📄 Pagination | pagesPerTag limits result pages for each tag. The number of post rows can be smaller than the website’s page window. |
| 🔐 Login required | No |
| ⚡ Processing | Up to 5 HTTP requests concurrently with automatic retries |
| 💾 Delivery | One Apify dataset view, useful flat columns and complete nested JSON |
What the Tumblr Tag Posts scraper collects 📦
The Actor follows the public feed behind a Tumblr tagged page. It keeps post records and leaves website navigation or promotional modules out of the output.
Data can include:
- Post IDs, canonical links, source blog, publication dates and tags
- Available text, summaries, content blocks
- Image variants, video references and link previews when present
- Visible note, like, reblog and reply counts when supplied
- Original and parent reblog references, with the available reblog trail
How to collect tag feed posts from Tumblr 🚀
- Enter one or more supported inputs in
inputList. - Set the result-page budget for each input.
- Start the Actor.
- Open the Posts dataset view and review the individual records.
- Export the dataset or retrieve it from your application.
pagesPerTag limits result pages for each tag. The number of post rows can be smaller than the website’s page window.
Tumblr tag feed posts data and complete output 📦
| Field | Type | Meaning |
|---|---|---|
status | string | Result status: success or failed. |
input | string | Original submitted input. |
id | string or null | Identifier of this object, preserved as a string. |
url | string or null | Public source URL for this object. |
blog_name | string or null | Name of the blog associated with this post or trail entry. |
blog_uuid | string or null | UUID of the blog associated with this post or trail entry. |
blog_title | string or null | Available title of the source blog. |
blog_url | string or null | Public URL of the source blog. |
blog_avatar_url | string or null | Available avatar URL of the source blog. |
post_type | string or null | Post type supplied by Tumblr; content blocks describe the actual components. |
original_type | string or null | Original post-type value when supplied by Tumblr. |
summary | string or null | Public post summary returned by Tumblr. |
text | string or null | Combined available text from the reblog trail and the current post. |
tags | array or null | Available tag values associated with the post or interaction. |
published_at | string or null | Publication time in an ISO-formatted date string when supplied. |
timestamp | integer or null | Source Unix timestamp in seconds; fractional precision is retained when supplied. |
note_count | integer or null | Public combined note count; not a guarantee of retrievable interaction records. |
like_count | integer or null | Public like count supplied for the post. |
reblog_count | integer or null | Public reblog count supplied for the post. |
reply_count | integer or null | Public reply count supplied for the post. |
is_nsfw | boolean or null | Source NSFW flag when supplied. |
is_blazed | boolean or null | Source flag indicating that the post is marked as blazed. |
media | array or null | Available media renditions and posters from the post and its reblog trail. |
media[].type | string or null | Object or content type supplied or normalized for this record. |
media[].role | string or null | Media role: a main media rendition or a poster image. |
media[].url | string or null | Public source URL for this object. |
media[].width | integer or null | Available image or media width in pixels. |
media[].height | integer or null | Available image or media height in pixels. |
media[].mime_type | string or null | Source media MIME type when supplied. |
content | array or null | Available structured content blocks retained in the parent record. |
content[].type | string or null | Object or content type supplied or normalized for this record. |
content[].text | string or null | Available text retained for this record. |
content[].subtype | string or null | Content-block subtype when supplied, such as a text presentation style. |
content[].url | string or null | Public source URL for this object. |
content[].data_json | string or null | Complete source content block serialized as a JSON string. |
trail | array or null | Available reblog-trail entries, preserving blog, post and content references. |
trail[].blog_name | string or null | Name of the blog associated with this post or trail entry. |
trail[].blog_uuid | string or null | UUID of the blog associated with this post or trail entry. |
trail[].blog_url | string or null | Public URL of the source blog. |
trail[].post_id | string or null | Source post ID associated with this interaction or trail entry. |
trail[].text | string or null | Available text retained for this record. |
trail[].content | array or null | Available structured content blocks retained in the parent record. |
trail[].content[].type | string or null | Object or content type supplied or normalized for this record. |
trail[].content[].text | string or null | Available text retained for this record. |
trail[].content[].subtype | string or null | Content-block subtype when supplied, such as a text presentation style. |
trail[].content[].url | string or null | Public source URL for this object. |
trail[].content[].data_json | string or null | Complete source content block serialized as a JSON string. |
reblogged_from_id | string or null | Immediate source-post ID of the reblog when supplied. |
reblogged_from_name | string or null | Immediate source blog name of the reblog when supplied. |
reblogged_from_url | string or null | Immediate source-post URL of the reblog when supplied. |
reblogged_root_id | string or null | Root or original post ID of the reblog when supplied. |
reblogged_root_name | string or null | Root or original blog name of the reblog when supplied. |
reblogged_root_url | string or null | Root or original post URL of the reblog when supplied. |
text combines available text from the reblog trail and the current post. The content array preserves individual content blocks; each data_json string contains the complete source block, including type-specific image, video, link or poll data. The media array keeps available renditions and posters with their source context. IDs remain strings so large Tumblr identifiers retain their exact digits.
Every top-level output field appears in these complete examples. The success example is normalized from a public response; its values are a snapshot and can change. Nested arrays remain inside their parent result.
Complete representative success result:
Complete failed result:
A failed row preserves input, sets status to failed, and sets every other top-level field to null. The run log records the reason. Optional successful fields can be null or empty when Tumblr does not supply them. Object fields are exposed through useful columns in the single Posts view; arrays are not expanded into extra result rows.
Input requirements and pagination settings ⚙️
| Parameter | Type | Required | Default | Rules |
|---|---|---|---|---|
inputList | array of strings | Yes | None | Tumblr tag names, hashtags or public tumblr.com/tagged URLs. At least 1 item. |
pagesPerTag | integer | No | 1 | Maximum result pages per input. Setup requests do not count as pages. Stops when the source has no next page or repeats a continuation. Actual rows per page can vary. Minimum 1. |
Enter supported tag names or Tumblr /tagged/ URLs. This Actor uses the dedicated tag feed rather than text-search results.
Supported examples include art, #art and https://www.tumblr.com/tagged/art. Tags must be nonblank and contain at most 256 characters. A /search/ URL belongs in a search Actor.
Duplicate normalized inputs are processed once. Within the collection for one source input, repeated records are removed while distinct interactions or objects remain separate. The same object returned for different source inputs retains its source relationship.
The first result page counts as page 1. Public-page preparation and metadata lookups do not consume result pages. Collection stops at your page budget or the end of the available list. A short page alone does not mean that the list has ended.
Tumblr tag feed posts use cases 🎯
Tag-focused editorial research
Collect a sample from a known topic feed with the source links needed for review.
Visual reference discovery
Review available image and video references while keeping post attribution.
Tag co-occurrence analysis
Export post tag arrays for your own analysis of related terms.
Pricing and saved-result behavior 💰
Check the Actor’s Pricing tab for the active pricing model and current rate. Store settings can change, so this README does not claim a fixed price or runtime.
Under dataset-item pricing:
- Each successful result represents one post for its source input.
- An invalid or unavailable input, an input with no accessible results, or an exhausted request can produce a
failedrow. - Retry attempts and supporting requests do not create extra dataset rows by themselves.
- Nested media, profile information and other arrays remain part of their parent row.
- A normal empty continuation after earlier successes creates no additional row.
- Saved failed rows are not assumed to be free; check their treatment in the active pricing configuration.
More inputs and larger page budgets can produce more saved rows. Start with a small run and check actual usage before increasing the workload.
Tumblr tag feed posts API 🔌
Replace $ACTOR_ID with the identifier shown in this Actor’s API tab and $APIFY_TOKEN with your Apify token.
Download the dataset in JSON, CSV, Excel or other formats available in the Console, or retrieve it through the Apify API. Use schedules, webhooks and Apify integrations to connect results to Google Sheets, Make, Zapier, cloud storage or your own application. These connections are configured separately by the user.
Reliability, retries, and public-data limits ⚠️
Collection uses pure HTTP with up to five concurrent requests. Invalid syntax and confirmed missing, removed or unavailable targets stop without unnecessary retries. Temporary network or proxy failures, timeouts, blocking responses, malformed data, throttling and server errors allow up to five total attempts per request.
Successful earlier pages remain saved if a later request fails. A normal end after saved results is not retried. An input with no accessible results can receive a failed row; that alone does not prove that its underlying source does not exist. An exhausted later request can add a failed row while preserving previous output.
The available post formats include text, images, video, links and poll metadata. Poll vote totals and audio coverage are not promised. A reblog can have no new text while its content remains in the reblog trail. Media references are returned when available; media files are not downloaded and their links can expire. The website controls tag-feed ranking and public availability. A tag feed is not a complete archive of all posts carrying that tag.
Tumblr controls public availability, ranking and optional fields. Result counts can be affected by duplicates, removed content and changes during a run. A page budget is a collection limit, not a promise of exhaustive coverage.
An invalid string within a valid input list does not stop other inputs. Invalid overall configuration, such as a non-string list item or a wrong page-count type, exits before source requests. Startup failures, unavailable dataset storage or an unrecoverable result-save error can still stop the whole run. A failed save is not retried as a new scraping request.
Frequently asked questions ❓
Is this text search?
No. It collects the dedicated Tumblr feed for a specified tag. Use Post Search Scraper for text-search queries.
Does it guarantee every post with that tag?
No. It follows the public feed within the selected page budget.
Does it keep the content of reblogs?
Yes. Available content and reblog-trail data remain in the parent post record. A post can legitimately have no new text of its own.
Does it require a Tumblr account or personal cookies?
No. You do not need to provide a Tumblr account, password or personal session cookie. Collection uses HTTP without opening a browser.
What happens to invalid or unavailable inputs?
Invalid individual inputs are recorded as failed without a source request. Confirmed missing or unavailable targets stop without unnecessary retries. Temporary failures allow up to five total attempts per request; other inputs and earlier saved results remain available.
Can I export results or run the same input again?
Yes. Export the default dataset or retrieve it through the Apify API. You can create an Apify schedule and connect completed runs to your own workflow.
Support, responsible use, and related actors 🛟
For a reproducible issue, use the Actor’s Issues tab and provide the run ID, approximate time, a safe public input, expected behavior and actual result. Include the mode or page budget when relevant. Never share access tokens, personal cookies or proxy credentials.
Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, analyzing or redistributing collected information.
