Patreon Collections Scraper
Pricing
from $1.00 / 1,000 results
Patreon Collections Scraper
Collect Patreon creator collections or individual collection details with titles, descriptions, covers and post 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
3 days ago
Last modified
Categories
Share
List a Patreon creator’s public collections or extract a selected collection by URL. Patreon Collections Scraper saves one collection per row with its title, description, cover, post count, dates and source links.
Map a creator’s series, courses or themed groups before choosing which posts to collect. A direct collection lookup uses the same result schema as the creator’s collection list.
| At a glance | Details |
|---|---|
| 📥 Input | Enter creator names or creator/Collections URLs to list collections, or collection URLs/numeric collection IDs for individual details. |
| 📤 Output | One collection per success row with the input source retained |
| 📄 Pagination | Result pages per input; page sizes and availability are controlled by Patreon |
| 🔐 Login required | No |
| ⚡ Processing | Up to 5 HTTP requests concurrently; up to 5 attempts for temporary failures |
| 💾 Delivery | One Apify dataset view with individual records and complete nested JSON |
What the Patreon collections scraper collects 📚
The Actor reads public collection metadata and follows pagination when the input identifies a creator. It keeps the collection as one result, rather than expanding its posts into additional rows.
Data can include:
- Collection ID, canonical URL, title and description
- Created and edited dates supplied by the source
- Post count, order setting and layout when available
- Cover images and public preview references
- Source creator and collection context for subsequent post collection
How to collect collections from Patreon 🚀
- Enter one or more supported inputs.
- Set the page budget and any collection option you need.
- Start the Actor.
- Open the Collections dataset view and review success or failed rows.
- Export the dataset or retrieve records from your application.
The page setting applies to a creator’s collection list. A direct collection input is an individual lookup and does not paginate the posts inside it.
Patreon collections output fields 📦
| Field | Type | Meaning |
|---|---|---|
input | string | Original submitted input. |
status | string | success for a collected entity; failed for an invalid, unavailable or exhausted input. |
id | string or null | Id when supplied by Patreon. |
type | string or null | Type when supplied by Patreon. |
url | string or null | Url when supplied by Patreon. |
title | string or null | Title when supplied by Patreon. |
description | string or null | Description when supplied by Patreon. |
created_at | string or null | Created at when supplied by Patreon. |
edited_at | string or null | Edited at when supplied by Patreon. |
post_count | integer or null | Post count when supplied by Patreon. |
collection_type | string or null | Collection type when supplied by Patreon. |
post_sort_type | string or null | Post sort type when supplied by Patreon. |
default_layout | string or null | Default layout when supplied by Patreon. |
thumbnail_url | string or null | Thumbnail url when supplied by Patreon. |
thumbnail_versions | array or null | Thumbnail versions when supplied by Patreon. |
cover | object or null | Cover when supplied by Patreon. |
post_ids | array or null | Post ids when supplied by Patreon. |
creator | object or null | Creator when supplied by Patreon. |
page | integer or null | One-based main result page. Null for an individual detail lookup. |
Nested field structure:
thumbnail_versions[]:name,url.cover:id,media_type,file_name,mime_type,size_bytes,state,url,download_url,width,height,duration_seconds,thumbnail_url,image_versions.cover.image_versions[]:name,url.creator:id,name,url,avatar_url,currency.
The examples below use normalized public response data. Values are snapshots and may change; every top-level output field is included. Different media variants and nested objects remain inside the same row.
Complete representative success result:
Complete direct-collection result:
Complete failed dataset item:
A failed row preserves input, sets status to failed, and sets every other top-level field to null. The reason is written to the run log. Optional successful values remain null or empty when Patreon omits them. The single dataset view exposes object fields as useful columns; arrays are kept in their parent row rather than expanded into additional rows or views.
Input and pagination settings ⚙️
| Parameter | Type | Required | Default | Rules |
|---|---|---|---|---|
inputList | array of strings | Yes | None | Enter creator names or creator/Collections URLs to list collections, or collection URLs/numeric collection IDs for individual details. |
pagesPerCreator | integer | No | 1 | Maximum result pages per input. Preparation requests do not count. Ignored for a direct collection or product detail input. Minimum 1. |
Enter supported creator inputs to list collections or a canonical collection URL for one collection. Use Collection Posts Scraper to collect the contents of a selected collection.
Use supported Patreon paths on www.patreon.com or patreon.com. HTTPS is required for full URLs; those two hosts can also be entered without the scheme. URLs with credentials, custom ports or unsupported paths are not accepted. A leading @ is accepted for plain creator names; names are normalized. Canonical creator URLs and supported /c/ or /cw/ creator paths are accepted. A numeric input means a collection ID, not a campaign ID.
Duplicate normalized inputs are processed once. A returned identifier is deduplicated within the pagination of one source input; the same object found under different source inputs retains each source relationship.
The first result request counts as page 1. Source validation and preparation requests do not consume result pages. A short or filtered page can continue if it supplies a usable cursor. Collection stops at the page budget or the end of pagination; a repeated cursor does not trigger an endless loop. A direct collection lookup ignores the list-page budget and returns the individual target in the same view.
Patreon collections use cases 🎯
Creator collection maps
List the thematic groups or series of a known creator with titles, descriptions and counts. Retain collection URLs for selecting later work.
Course and series research
Inspect a chosen collection’s description, cover and organization. Public metadata does not imply access to paid lessons or media.
Collection change snapshots
Repeat collection queries and compare titles, descriptions or returned counters in your own store. Changes can reflect editing and availability as well as new posts.
Pricing and saved-result behavior 💰
Check the Actor’s Pricing tab for the active charging model and current rate. Store settings may change, so this README does not state an unverified fixed price or runtime.
Under dataset-item pricing:
- Each unique success result represents one collection for its source input.
- An invalid or unavailable input, an input with no accessible results, or a request that exhausts retries can produce a
failedrow. - Retry attempts and supporting metadata requests do not create extra dataset rows by themselves.
- Nested media, tiers, poll choices and source fields stay inside their parent result when relevant.
- A normal empty continuation after earlier successes creates no additional result row.
- Saved failed rows are not assumed to be free. Check the active pricing configuration for their treatment.
Larger page budgets and more inputs can produce more saved rows. Start with a small run and check actual usage before increasing the workload.
Patreon collections API 🔌
Replace $ACTOR_ID with the identifier shown in this Actor’s API tab and $APIFY_TOKEN with your Apify token.
Download JSON, CSV, Excel, XML or other formats available in the Console, or retrieve the dataset through the Apify API. Schedules, webhooks and Apify integrations can connect results to Google Sheets, Make, Zapier, n8n, cloud storage or your own backend. These are connection options rather than integrations already configured by the Actor.
Reliability, retries, and public-data limits ⚠️
Collection uses pure HTTP with up to five concurrent requests. Invalid syntax and confirmed missing, removed or inaccessible targets stop without unnecessary retries. Temporary network or proxy failures, timeouts, blocking responses, malformed data, throttling and server errors are retried up to five total attempts per request.
Earlier successful pages remain saved when a later request fails. A normal end after previously saved results is not retried. An input that produces no accessible results can receive a failed row; this does not by itself prove the underlying account or collection does not exist. A later exhausted request can append a failed row while keeping earlier output.
Patreon controls public availability, ranking, fields and pagination. Private, deleted, restricted or otherwise unavailable data can be omitted. Counts can change during collection, and media links can expire. Successful HTTP research confirms the supported request paths and pagination on tested sources, rather than future availability or exhaustive coverage.
A collection count is metadata and does not guarantee that every post is public or available. Collection cards can describe subscriber-only series. Cover media and post identifiers do not grant access to protected post content.
An invalid string within a valid input list does not stop other inputs. A configuration that fails validation, such as a non-string list item or an invalid page-count type, exits before requests start. Infrastructure errors such as startup failure, unavailable dataset storage or an unrecoverable result-save error can stop the whole run. A failed dataset save is not retried as a new scraping request.
Frequently asked questions ❓
Does it collect the posts inside every collection?
No. This Actor lists collections and their metadata. Send selected collection URLs to Collection Posts Scraper to collect their public-facing post records.
Can I submit a single collection URL?
Yes. A supported collection URL returns that collection in the same schema, without scanning the creator’s whole collection list.
Does a collection with 96 posts yield 96 rows here?
No. It yields one collection row. The post count is a field in that record rather than the number of rows returned by this Actor.
Does it require Patreon login or personal cookies?
No. The Actor uses HTTP requests from the public website. It does not require a Patreon account, password or personal session cookie, and does not launch a browser.
What happens to invalid or unavailable inputs?
Invalid individual inputs are saved as failed rows without a source request. Confirmed unavailable targets stop without unnecessary retries. Temporary failures allow up to five total attempts; other inputs and previously saved results remain available.
Can I export results or schedule runs?
Yes. Download the default dataset in supported formats or retrieve it through the Apify API. Apify schedules and completion webhooks can connect repeated 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, safe public input, expected behavior and actual result. Include the selected mode or page count when applicable. Do not share access tokens, cookies or proxy credentials.
Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, analyzing or redistributing collected information.
